The Group module allows for "grouping" two or
more Study Units for comparison or other purposes. Study Units can be
grouped as series or topical collections in a single or hierarchical
grouping. The Group module identifies the type of group through the
use of a grouping grid that covers:
The grid was established to provide programmers with information on
how the studies within the Group relate to each other on each of these
dimensions. Decision Trees are provided to assist the user in
completing the grid in a consistent manner
(see Part II: High-Level
Documentation).
| import |
reusable.xsd |
ddi:reusable:3_0 |
| import |
archive.xsd |
ddi:archive:3_0 |
| import |
comparative.xsd |
ddi:comparative: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 |
studyunit.xsd |
ddi:studyunit:3_0 |
| import |
ddiprofile.xsd |
ddi:ddiprofile:3_0 |
| element |
Abstract |
Human-readable summary of the grouped material. |
| complexType |
ConceptType |
Allows for inclusion of a fully marked up Conceptual Components module or referencing such a module that is external to the
instance.
|
| element |
Concepts |
Lists, or references, the concepts describing the data that are being documented. |
| element |
DDIProfileReference |
References a DDI Profile used by the group or resource package. |
| element |
DataCollection |
Shared documentation regarding data collection for all members of the group, subject to over-rides at a lower level. |
| complexType |
DataCollectionType |
Allows for inclusion of data collection information that is common to all members of the group, or referencing external data
collection information.
|
| simpleType |
DataSetGroupCodeType |
Indicates how all members of the group are related in terms of physical data products in relation to data collection efforts.
These relationships are inferred by the markup author, and should be considered as her/his own interpretation of the data.
|
| simpleType |
GeographyGroupCodeType |
Indicates how all members of the group are related along the dimension of geography. These relationships are inferred by the
markup author, and should be considered as her/his own interpretation of the data.
|
| element |
Group |
Groups are used to document related data. They may contain subgroups or individual study items, and may also contain metadata
which is applicable to all members of the group, and is subject to over-rides at the lower levels. Thus, metadata is inherited
down the grouping structure. The purpose of groups is described using the attributes which summarize relationships along the
dimensions of time, panel, geography, instrument and language. These attributes allow the purpose to be machine-actionable,
while the group also includes an element for describing the purpose in human-readable format.
|
| complexType |
GroupType |
Groups are used to document related data. They may contain subgroups or individual study items, and may also contain metadata
which is applicable to all members of the group, and is subject to over-rides at the lower levels. Thus, metadata is inherited
down the grouping structure. The purpose of groups is described using the attributes which summarize relationships along the
dimensions of time, panel, geography, instrument and language. These attributes allow the purpose to be machine-actionable,
while the group also includes an element for describing the purpose in human-readable format.
|
| simpleType |
InstrumentGroupCodeType |
Indicates how all members of the group are related in terms of the instruments used to collect data. These relationships are
inferred by the markup author, and should be considered as her/his own interpretation of the data.
|
| simpleType |
LanguageGroupCodeType |
Indicates the panel relationships among all Study Units within the group and its sub-groups. This is an assertion of the relationship,
and it is incumbent on the creating user or application to make sure that the assertion is true.
|
| element |
LogicalProduct |
Shared documentation regarding the logical data products of all members of the group, subject to over-rides at a lower level. |
| complexType |
LogicalProductType |
Allows for inclusion of a logical product that is common to all members of the group, or referencing an external logical product. |
| simpleType |
PanelGroupCodeType |
Indicates how all members of the group are related in terms of type of panel. These relationships are inferred by the markup
author, and should be considered as her/his own interpretation of the data.
|
| element |
PhysicalDataProduct |
Shared documentation regarding the physical data products of all members of the group, subject to over-rides at a lower level. |
| complexType |
PhysicalDataProductType |
Allows for inclusion of a physical data product for reuse by reference. |
| element |
Purpose |
Human-readable explanation of why the creator published these objects. |
| element |
Reference |
References a module that is external to the group, sub-group, or resource package. |
| element |
ResourcePackage |
The Resource is a specialized type of Group which is intended to hold re-usable metadata such as Category Schemes, Variables,
etc. It is placed in the Resource construct for the purposes of being included by reference in other Groups and StudyUnits
which describe studies, but does not directly describe existing studies itself.
|
| complexType |
ResourcePackageType |
The Resource Package is a specialized structure which is intended to hold reusable metadata such as Category Schemes, Variable
Schemes, etc. These are placed in the Resource Package for the purpose of being included by reference in Groups and StudyUnits.
The Resource Package has a similar structure to the Group.
|
| element |
StudyUnit |
Description of an individual study being documented as a member of the group. The study unit description inherits all metadata
found at higher levels - that is, all metadata and documentation describing the groups and subgroups of which the study unit
is a member. This metadata and documentation may be over-ridden within the study unit.
|
| complexType |
StudyUnitType |
Allows for inclusion of a study unit that belongs to the group as a direct child. Subgroups may also contain study units,
and individual study units and subgroups may be members of a single group. Study units can be included in any group or subgroup
either as in-line documentation/metadata or by reference.
|
| element |
SubGroup |
Subordinate group which inherits all the metadata provided in the higher-level groups and subgroups of which this subgroup
is a member, subject to over-rides within the sub-group itself.
|
| complexType |
SubGroupType |
The subgroup element is a container for a group that is a child of a higher-level group described in this module, but may
also be a parent to other (subordinate) groups. A group can be fully described, or just referenced, within its subgroup container.
|
| simpleType |
TimeGroupCodeType |
Indicates how all members of the group are related along the dimension of time. These relationships are inferred by the markup
author, and should be considered as her/his own interpretation of the data.
|