General Questions and Notes:
(includes specific problems which are extracted to the right column)
(includes specific problems which are extracted to the right column)
DDI 4 xml example - ICPSR Study 8344
Documenting DDI 4 Codebook View like ODM
-ODM Example
World Bank DDI 4 xml example
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Clear guidance on where to start - DDI element, rootClearly define what abstract classes meanDefine what attributes, properties, and relationships mean in the context of the model. This should be spelled out for the layperson with specific examples.Annotation will also require guidance and when and where to use.Specific guidance on creating IDs, by hand.Clarification of what CollectonTypes mean, bags and sets.Clear explanation of how to record what used to be part of the methodology section in DDI 2, such as sampling procedures, weighting, etc. The added flexibility of doing this in 4 means it needs more guidance.The relationships between instance, represented, and conceptual for both variables and questions needs to be made VERY clear.Also, clear language around DataStore and the PhyscialLayout options.Locators are buried quite deep. Clear language needed. |
Expand | ||
---|---|---|
| ||
General:Has a map in mind from 2 and 3."This is even more complicated than 3.0"The issues with cross-referencing and complication. See Thursday notes.Specific questions: Where to start? What is the root element? Need a wrapper.What is the attribute type of DDI element - look at attributes (manual process different)Chose DDI, gives you documentionformation - fixedClear instruction on where to use Annotation and what to put in it (documentinformation/study, etc.). Describing the instance vs the study.STUDY:Under hasAnnotation:
|
Expand | ||
---|---|---|
| ||
Clarification of language around object properties (sub-elements) and attributes
|
Expand | ||
---|---|---|
| ||
Continuing Variable:Question: IDs in 4 are plain text, does this make it more difficult for software to parse, e.g. Codelist contains code, code denotes category. Class name has same type of content.Code and codeItem: why is this necessary when a code item can only contain one code? Redundant? Code without codeItem? - discussed. See Thursday notes.Time to discuss IDs! The difficulty of programming to all of the cross-references. External references would not be as complicated, would be to another object and then parse that object. - discussed. See Thursday notes.How to group variables? - on the task listRange and valid range - do it in the ValueandConceptDescription , minimum value inclusive, exclusive, etc.FrequencyHow to input frequencies? - not available - on task list.QuestionInstanceQuestion requires RepresentedQuestion, which is not in the codebook view. - fixedAble to create a represented question when using the whole DDI schema - see task listLayoutWe cannot instantiate a physical layout in the codebook view. - Need to use a specific type, so rectangularLayout or event dateNo location attributes in DD4 - locaters have been added as valuemappings in rectangularLayout |
Expand | ||
---|---|---|
| ||
Mehmood Session:He started with Larry's data description of a csv example. He will take study description information from Sanda's work.Goal is to have the same elements that the World Bank uses.Worked in DataStore for the record counts, missing values, version rationale, etc.He couldn't find where to put processing checks.The name of data file should be in dataStore (logical), but is missing one for the physical IMPORTANTWorld bank thinks of variables as part of a data file, don't think of them as outside the file - in 4 he defined as instance variables (with no link) then did logicalRecordLayout that links the variables to the data file.Rectangular layout contains ValueMappings, helpful for the csv that they are generating.Summary statistics are missing - World Bank uses a lot - lost these when PhysicalInstance went away.Will go home and finish and leave notes in the xml, and fill in from Sanda's example.More work on filling in all of study description fields in 4 should be done.Mehmood to send spreadsheet of World Bank 'profile' from nesstar to Sanda to test furtherSANDA session -Methodology - Use subjectofMethodology to describe different pieces, weighting, sampling, etc. Problem is how do you control who uses what controlled vocabulary. The advantage of 2 is that these fields are set and clear. Could you hard-wire the external controlled vocabulary into the software tool?File issue - clean up use of content vs. languagespecificstring - need to identify all points where attributes point to complexdatatypesBeing able to lock it down, constraining the extensibility somehow? Using the World Bank as a use case.
|
Expand | ||
---|---|---|
| ||
Sanda's notes from her work Friday morning.-Used the new updated Build.-The issue with the reference to Conceptual Instrument only (when we needed to refer to the Implemented Instrument) has been fixed. |
Panel | ||
---|---|---|
| ||
Code is redundant when you already have a codeItem. coverageDate links to referenceDate which inherits typeOfDate from AnnotationDate ? General question about why different classes if they have same type (Date, annotationDate, ReferenceDate). SamplingAlgorithm and Algorithm (from Study), what is their purposehow to use? Could you hard-wire the external controlled vocabulary into the a software tool? In general thinking about a way to control the extensibility and using the World Bank as a use case. |
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
General
Study
Variables
Frequency
Question
Layout
Coverage
|
Attachments |
---|