Simple Codebook Meeting MinuteMinutes February 2, 2015 Present: Dan Gillman, Wendy Thomas, Mary Vardigan, Oliver Hopt, Larry Hoyle, Steve McEachern, Mary Vardigan The Simple Codebook committee will now be chaired by Dan Gillman as Wolfgang is not able to chair currently. This group has been in a holding pattern because we are waiting on the results of other groups. However, it was suggested that we look at the Codebook 2.5 in comparison of DDI 3.*. XML permits a detailed description of elements and this is part of the distinction between 2 and 3. But UML doesn't allow this and doesn't account for nesting and levels of detail. We should try to incorporate what is in Version 2 into the model as best we can. We as a group should try to build this. One additional possible other advance would be that we could then have a single model to account for both Codebook and Lifecycle. Both views would be under one spec in this approach. Is referencing and reusability a distinction between the two versions that we should take into account? Should it be communicated to the modeling team that we may not need the complexity? For users who want to describe their data, they should be able to write a description and fit it into a framework. If you want to have interoperability with other systems, then it is an issue. For the standalone one-off research project, they will not be reusing variables and questions, but for longitudinal and research across languages and cultures, this is important, harmonize across questionnaires, reuse across time, etc. Maybe this is Complex Codebook? We need a distinction between the user perspective and the technical perspective. Simple and complex need to be interoperable. It's necessary to reduce the complexity of what is modeled in the library by choosing the simple cases. One of the decisions for DDI 4 is to make everything identifiable and drop the container aspect of identifiability. This takes away a lot of the complexity. From a marketing perspective, we need to distinguish between DDI Codebook version and Simple Codebook view. Looking at what is in 2 now will be required and we need to lay out what we need to account for. In the study section for DDI Codebook, there were a number of elements that allowed you to provide a high level text description of various methodological things. Preserving that is important. |