StudyUnit

Package: 
Is Abstract: 
no
Is Pattern: 
no
Definition: 

A primary packaging and publication module within DDI representing the purpose, background, development, data capture, and data products related to a study. In DDI a study is defined as a single coordinated set of data collection/capture activities, such as a one-time survey or a single iteration of a multi-year repeated study (such as one year of a longitudinal survey). The StudyUnit brings together all of the components of the study including the description of its purpose, funding, quality statements, data collection and capture methods and activities, processing activities, and a description of the resulting data (description of its intellectual or logical content plus a description of its physical store). A study unit may have only a single data collection or capture process resulting in one or more data products (i.e., Census). A complex study unit may contain multiple means of data capture that are integrated into one or more data products (i.e., a medical study collecting bio-markers, patient background, health care service information, etc.). A longitudinal study with multiple waves or iterations of data collection is considered to be a group of studies, each wave or iteration captured as a single study unit. As a primary packaging module, the Study Unit contains a full citation, abstract, authorization information, a universe reference, series statement, quality statement, information on post study evaluation, funding information, budget, purpose, coverage, type of analysis units covered, kind of data, other materials, a list of required resource packages, embargoes, the conceptual components (universe, concept, data element, geographic structure and locations), data collection, logical products, physical data products, physical instance, archive, and DDI profile. The maintainable elements within a Study Unit may be included in-line or by reference.

Property: 
NameCardinalityDatatypeDescription
abstract
0..1
An 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. Abstract supports multiple language versions of the same content as well as optional formatting of the content.
purpose
0..1
The purpose of the study, why the study took place. 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. Legal or other authorization should be provided in detail within AuthorizationSource. Purpose supports multiple language versions of the same content as well as optional formatting of the content.
analysisUnit
0..n
Allows the use of a controlled vocabulary to list all of the units of analysis used in the study. Should be repeated to describe multiple units of analysis.
analysisUnitsCovered
0..1
A narrative of the units of analysis in the study unit. Uses an InternationalString to support multiple languages.
documentedVersion
0..1
Text describing the version of the Study.
Relationship: 
NameTarget ObjectDescriptionSource cardinalityTarget cardinalityRelationship type
authorizationSource
Identifies the authorizing agency for the study and allows for the full text of the authorization (law, regulation, or other form of authorization). May be used to list authorizations from oversight committees and other regulatory agencies.
0..n
1..1
Aggregation
universeReference
Reference to the universe statement from the universe scheme, describing the group of persons or other elements that are the object of research and to which any analytic results refer. Age, nationality, and residence commonly help to delineate a given universe, but any of a number of factors may be involved, such as sex, race, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. In general, it should be possible to tell from the description of the universe whether a given individual or element (hypothetical or real) is a member of the population under study. A universe may be described as "inclusive" or "exclusive". This StudyUnit level reference is normally to the top level of the UniverseScheme.
0..n
0..n
Aggregation
seriesStatement
A study, particularly one in a series, may be the result of two series merging into a single study. The new study belongs to both series. For example, Niger now fields the UNICEF Multiple Indicators Cluster Survey (MICS) and the Demographic and Health Survey as a single merged instrument.
0..n
0..n
Aggregation
qualityStatementReference
A reference to a Quality Statement pertaining to the quality of the study overall, metadata, or data to which it is associated. Quality statements may be related to external quality standards.
0..n
1..1
Aggregation
exPostEvaluation
An evaluation of the study process, often taking place after the completion of the study. These may include issues such as timing of the study, sequencing issues, cost/budget issues, relevance, institutional or legal arrangements etc. of the study. If the study is part of a series or group (i.e., a single wave in a longitudinal study) this may include evaluation of earlier waves which resulted in changes to the current wave.
0..n
1..1
Aggregation
fundingInformation
Contains details of the study unit's funding, including information about grants, agencies, etc.
0..n
1..1
Aggregation
studyBudget
This describes the overall budget of the study. It can be repeated for distinct budget activities. It contains a structured description and one or more budget documents described by an OtherMaterial type.
0..n
1..1
Aggregation
coverage
Describes the coverage of the study unit. Detailed information on Topical, Temporal, and Spatial Coverage is contained here. Note that Coverage at this level should be inclusive all lower level modules or section. Lower level descriptions serve to constrain coverage within the scope described here.
0..1
1..1
Aggregation
kindOfData
Briefly describes 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. Supports the use of an external controlled vocabulary.
0..n
1..1
Aggregation
requiredResourcePackages
Specifies by reference the ResourcePackages required to resolve the Study. This list is informational and assists in creating full transmissions of metadata or creating archival packages. Primarily used after the instance is relatively stable and published.
0..1
1..1
Aggregation
embargo
Embargo information about the study unit. References to embargo information in this section can be made from individual variables.
0..n
1..1
Aggregation
dataCollection
changed relationship to new object. Documents the content of the Data Collection activities used in this study; development of data collection processes, questions, question flows (control constructs), data collection instrument, instructions, processing events and instructions, methodology, etc.
0..n
0..n
Aggregation
agent
Replaced the Archive by Agent. Archive serves as a packet containing both persistent and transient information. Describes archive-specific material including item record information as well as lifecycle information. The metadata in the package is divided into elements that are persistent (should remain with the Study Unit through its life-cycle), and transient (pertinent only to the Study Unit as held by that archive).
0..n
0..n
Aggregation
ddiProfile
Contains a DDI Profile which is used by the study unit.
0..n
1..1
Aggregation
otherMaterial
Contains references to other materials relevant to the study unit, whether in DDI form or external. Links can be made from items in this section to any identifiable element in the instance. Best practice is to include OtherMaterial inside the maintainable containing the objects that are related to the OtherMaterial.
0..n
0..n
Aggregation
annotation
The basic annotation or citation for the study unit. At minimum a title should be provided.
0..1
0..n
Aggregation

Stage:

DDI 3.2: 
s:StudyUnitType
Is extendable: 
Is property: 
0
RDF Mapping: 

Comments

We supoose that a general way to create "Note" elements for any object will be created. So we don't create a separate "Note" object for the StudyUnit

We need several properties from the ConceptualComponent, but since there is work going on there, we didn't specify the relations/properties.

All organization and individual names, contacts etc. can now be found under Agent.

I have removed BaseLogicalProduct and PhysicalInstance as they are no longer valid wrappers for the sets of information they contained in the past. As collections are instituted you will need to include the collections of information formerly held in LogicalProduct. In addition the PhysicalInstance has been recreated and renamed. You will need to identify the appropriate Data Set information.

Coverage was moved to relationship. Citation was moved to relationship as annotation.