Date
Attendees
- Ornulf, Wolfgang
Goals
- Detect links between SimpleCodebook and DataDescription and Instrument
Work
1) The Codebook use case implies that we need a lot of information about a dataset, its variables, and their question texts/descriptions
2) To find these additions to the Study level information in the codebook, a link is needed from the StudyUnit object, containing a DataCollection activity, to the dataset as modelled by the DataDescription group
3) The DataDescription package contains an object DataSet that in the simple case can be an equivalent to a data file (but also data stream etc...). Via DataSetStructure that is related to InstanceVariabe, which is the object that can give the Codebook most of the Variable object information that is needed.
4) Rather than linking directly fro StudyUnit-DataCollection to DataSet it would be possible to go the path via the Instrument as Defined by the DataCapture group. There is the object ConceptualInstrument that has an ImplementedInstrument with one or more ProcessSteps. These ProcessSteps can be an InstrumentComponent that may be a Capture that may be a Question which has e.g. a text property. The Capture (ans thus the Question) has a link to an InstanceVariable, and from there we can get all the Variable object information for the Codebook that is needed.
5) Due to simplicity of the model only on link from the StudyUnit to the needed objects should be modelled - if suffiecient. That would imply to use the latter (4) link in the model.
6) The Codebook use case could start with the object "DataSet" and get all information needed from there.