The Study Unit module encompasses the basic information on the individual study. It is the first module created along the
life cycle of the data and begins with an abstract and the purpose of the study. Background references can be noted in Other
Materials along with external copies of proposals or other related materials. In addition, Study Unit houses the list of concepts
(Conceptual Components) that the study is investigating or collecting data about. This module covers everything up to the
beginning of the Data Collection process. Once completed, this module will generally be passed along as a persistent module,
without changes, unless corrections are needed or future users impose alternative concept structures on the data. Note that
a Study Unit can have multiple Data Collection activities and that a study can result in one or more Logical Products (information
on variables, independent of physical representation).
| import |
reusable.xsd |
ddi:reusable:3_0 |
| import |
archive.xsd |
ddi:archive:3_0 |
| import |
conceptualcomponent.xsd |
ddi:conceptualcomponent:3_0 |
| import |
datacollection.xsd |
ddi:datacollection:3_0 |
| import |
logicalproduct.xsd |
ddi:logicalproduct:3_0 |
| import |
physicaldataproduct.xsd |
ddi:physicaldataproduct:3_0 |
| import |
physicalinstance.xsd |
ddi:physicalinstance:3_0 |
| import |
ddiprofile.xsd |
ddi:ddiprofile:3_0 |
| element |
Abstract |
A human-readable abstract of the study unit describing the nature and scope of the data collection, special characteristics
of its content. Note that detailed information on the purpose of the study and structured coverage information are to be entered
in Purpose and Coverage. During study development, or when creating documentation from incomplete legacy materials, this field
should contain an appropriate statement such as "Under development", "Unavailable", "Not provided by creator", or some other
similar statement
|
| element |
DDIProfileReference |
References a DDI Profile used by the study unit |
| element |
KindOfData |
Describes, with a string or a term from a controlled vocabulary, the kind of data documented in the logical product(s) of
a study unit. Examples include survey data, census/enumeration data, administrative data, measurement data, assessment data,
demographic data, voting data, etc.
|
| complexType |
KindOfDataType |
Describes, with a string or a term from a controlled vocabulary, the kind of data documented in the logical product(s) of
a study unit. Examples include survey data, census/enumeration data, administrative data, measurement data, assessment data,
demographic data, voting data, etc.
|
| simpleType |
KindOfDataTypeType |
Provides a description of the types of data described by the KindOfData element. |
| element |
Purpose |
The purpose of the study, in human-readable form. This should include detailed information on the investigator's primary study
questions or hypotheses as well as information on any legal basis for the data collection, such as laws requiring the collection
of census data for apportionment purposes. During study development, or when creating documentation from incomplete legacy
materials, this field should contain an appropriate statement such as "Under development", "Unavailable", "Not provided by
creator", or some other similar statement.
|
| element |
StudyUnit |
- |
| complexType |
StudyUnitType |
Describes the study unit which encompasses specified data collection processes as well as their resultant data products. This
includes all of it's associated documentation and metadata. A Study Unit corresponds to the "study" as described in a traditional
codebook, although a codebook may relate to only a single data product from the study. Typically, a 2.* or earlier version
can have its content marked up in DDI version 3.0 with a single study unit containing the bulk of the documentation and metadata.
Multiple data products from the same "study" (typically separate DDI instances in 2.* and earlier) can be combined in a single
3.0 instance. (See "DDI 3.0 Documentation, Part 1: Basic Structures" for more detail regarding the mappings between 2.* and
3.0.)
|
