Meeting: 2014-06-30

Attending: Guillaume Duffes, Dan Gillman, Larry Hoyle, Ørnulf Risnes, Steve McEachern, Wendy Thomas

Reviewed list of related package and view content from Wolfgang

Decisions:

There is currently a lot of duplication in the list and it needs to be normalized prior to review.

Steve will normalize the list and send it out to members later this week with the following instructions:

Review the list and do the following:

1. Add any unlisted objects that you would expect to find in a basic or simple codebook

2. For each item indicate if the item is one which would be required in order to publish the codebook or is one that would be useful to have in the codebook

3. Return your review to the group.

Unless other agenda items arise, schedule the next meeting after the deadline for returning reviews.

Process:

• Items that have agreement in terms of "required" will go into a basic view

• Items that have agreement in terms of "would like to see" will go into an "intermediate" view

• Items without agreement will be discussed and assigned during the next meeting

This may result in the creation of two "simple codebook" views and appropriate names should be determined.

Discussion:

Given the range of use cases (something above a simple data set to a simple study housed in an archive) it is difficult to determine what is meant by "simple". Rather than discuss in the abstract it may be helpful to get a list of objects one would like to see in a simple codebook from the members of group and then identify those objects that are considered to be the minimum requirement for publication. This may result is two levels for a simple codebook (basic and intermediate) but the approach would provide clear information on where there is consensus and where there is debate.

Statements that may help define the differences between these two levels:

• The bare minimum needed in order to publish (basic)

• What would you like to see in this view (intermediate)?

There has been a shift from the initial content creation in Drupal of a simple codebook "package" to the idea of a "view" and we need to reorient the Drupal content to this shift. In addition, packages and views relating to the simple codebook view that were not in existence when the work of this group was started are now more fully defined. The content of these packages and views needs to be considered when defining the view(s) of a simple codebook.

View orientation is liberating

• A view contains objects (it is not a compilation of views)

• A view (specific version) may be partially or fully support another view - the intent to do this should be noted in the description of the new view

The following process could be useful in defining the view(s) for a simple codebook:

Creating the list of objects for a simple codebook:

• Start with Wolfgang's list as an example, (normalized version of this list)

• What would you add?

• What would you like?

• What is required vs. what is optional (simple to intermediate)?

Create a view of Simple codebook in Drupal - using the final agreed upon list of a view

Note: Some of the objects being included are complex objects. These should then be reviewed to see if a simpler basic object of that type is needed. (I.e. we may only want to include a "stripped down" version in the view)

Steve will take a go at normalizing and send list out to group

Wolfgang can then enforce getting responses.

Meeting in two weeks:

• this week if possible for list out

• wish list turnaround

• may want to delay next meeting until after due date for getting lists back from members