| Info | ||
|---|---|---|
| ||
| Expand | ||
|---|---|---|
| ||
Simple Codebook Meeting 2016-11-22 Attendees: Dan Gilman, Oliver Hopt, Larry Hoyle We discussed a YAML template of the codebook view and looked at it in NotePad++. This revealed the complexity of the model (20992 lines in the template) which should probably be discussed in the Modeling Team. The YAML template was produced by a small Python program that reads the xmi.xml from the lion site, parses it and produces the YAML. We discussed the possibility of having a YAML template accessible for each DDI4 class either through the nightly build or from lion. The codebook YAML template is available in the list of files on the Simple Codebook Team page. |
| Expand | ||
|---|---|---|
| ||
Notes on Codebook meeting 13 September 2016 Participants: Dan Gillman, Steve McEachern, Larry Hoyle, Gillian Kerr Review of missing content in Data Description required by Codebook 1. Embargo for variables: Security, embargoes, access: 2. Variable "interval" Note that both of the above have "primitive data types" in ISO11404 (nominal - state, 3. Variable files suggest leaving this out and see if this is needed in the review. Note that the codebook approach here may be counter to the modelling strategy we have for DDI4 - it also makes reuse problematic. 4. Summary statistics suggest leaving this out of review and note that it has to be developed. We could note what they will be, and where they may be located (on the DataStore??). Suggest looking at how Lifecycle handles them (similar to a key-value pair) after the review is completed. (Conversation following with Wendy: probably attach with the physical file, but should not be tightly integrated). 5. Derivation Description (and related): suggest to be addressed by Methodology and Process Methodology items: need to be addressed by the Methodology group Other items: ACTION ITEM: responseUnit and analysisUnit should be discussed via email in the next two weeks |
...
| Expand | ||
|---|---|---|
| ||
Codebook meeting 2 February 2016 Attending: Dan, Michelle, Steve, Oliver, Jon, Larry, Jared There’s some lack of clarity about where this group is at. Discussed what to include in simple codebooks. One idea is to review the spreadsheet of common elements (summary of CESSDA) and build on that. Essentials seem to include: enough information to read the data into statistical package, label values, understand universe, understand what measure means so you can interpret the data, attribution information. Another idea is to look at examples of simple codebooks, identify what they use, and then map to a model. We need to be careful to keep things simple. Even older versions of DDI 2 weren’t exactly simple. If we nail down definitions, then do we make instances of previous versions incompatible? As we define what information elements we want in DDI 4.0, we can specify which element you want in 2 if you’re going backwards. Next steps:
|
...