| Info | ||
|---|---|---|
| ||
| Expand | ||
|---|---|---|
| ||
Present: Dan Gillman, Steve McEachern, Jared, Oliver Hopt, Gillian Kerr, Kristiyan Panayotov Gillian Kerr and Kristiyan Panayotov join the group, Steve and Jared we take care of access to websites and mailing lists. Continue of discussion on Variables in SCDecisions on the level of information we want to keep in and out of simple codebook should be left to the point, when the other views and packages are a bit more sattled. The main direction of the further discussion in the next meetings will therefore go on to the definition, what we would expact to be documented for a variable and its surrounding classes. Main Question: What do we wnat to seen in a codebook, especially a basic one? What is a variable? - What is the meaning of a variable? - Characteristic - Population - Is a variable the same, if everything is the same but the population? (Sex of humans and/or bears) - What are the values of a variable?
Extending the usecases especially from Gillian, which sounded to be quite complex while fitting into SC. |
| Expand | ||
|---|---|---|
| ||
Minutes Codebook 2016 – 03 - 01
Present: Michelle Edwards, Dan Gillman, Steve McEachern, Oliver Hopt, Jon Johnson, Larry Hoyle Reviewing Michelle’s addition to the view spreadsheet. We need a view Unclear if we need a package What other classes/objects are we likely to need? - Study - Contributor and a Role CV - Notes class Need something like 2.x Study Stats agencies may not need Study Michelle looked at DDI Lite and the “Archives using” column and cut out unused elements. She cut down the DDI-LITE profile even further to suggest items that we think are essential. Variable description looks like not being used by archives but we know we need that Column E has mapping to DDI4 Can we come up with an (incomplete list of methodologies that we need)? Last meeting: Discussion on methodology. We discussed the need for a reference document or a descriptive statement that we may wish to refer to for describing a methodology. We may have a need for a more detailed description, or even a call to a process, but this is an initial high-level description only. - Distinction between Usage (in the Methodology model) and a text description (what we are considering here). We would have a reference to the more detailed usage. - This will be raised by DG, LH and OH in the modelling group for a preferred approach. How do we handle a short descriptive statements in the codebook? A codebook will not necessarily have the detail to drive a process. What would a template have? There is usage in the methodology model but this is something higher level than that. A codebook would then have a reference to the more detailed metadata. Does the modeling group have a preferred approach to this? Bring this up at the modeling meeting tomorrow. What in DDI4 corresponds to the note in DDI-C?
VariablesDo we want to reproduce the variable cascade in a codebook? Could it just be the IV? Or will we need the references to further up the cascade - RV and CV In the current DDI4 model we have references in the InstanceVariable to RepresentedVariable and ConceptualVariable The discussion of the Variable use lead naturally into the link from Variable to Question. And there are also Variables do NOT have Questions (e.g. derived variables, instrument measures, etc.) What do we really want to be supporting in the Codebook view? Steve and Michelle to develop usecase(s) to identify requirements. What about references to reuse of other's materials/variables/etc. Larry suggests that the codebook should be able to reference such content, where it is available. The question becomes how to do that referencing, and to what extent? Steve and Jon's query is what form would that codebook take? Question mode has an impact – do we want to record this in a codebook. In multi-mode surveys in a codebook there could be different forms of the questions for each mode. Example BLS CES – multiple modes the codebook would need to account for all of that. When people think variables they think questions in the DDI2 world In DDI2 can’t really describe an instrument. Many variables don’t come from questions. A variable focus is more general than a question focus and should be our focus. DDI2.5 moves to a variable focus. How far should we move into a focus on questions? Steve and Michelle will put together a use case. Is a reference to Represented etc meaningful unless there is a repository containing it. Is a codebook for reuse? Information should be included by instance in the codebook but references to reused elements could be included. What if the target objects are not DDI encoded? Do we want references at each possible point? Or just at the InstanceVariable? What would a PDF look like? A weakness of a codebook is that it is stand-alone. We should have a side email discussion of how we include pointers. No one will want to retool existing study documentation. These features need to be optional. Two discussions for next meeting: 1. Steve and Michelle for Variable usecases 2. Larry and Dan to lead a discussion on what a "codebook" might look like in the 21st century / RDF / Linked Data world? How far can we move towards that new Codebook form?
|
...
| 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:
|
...