ResourcePackageType

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

The Resource Package is a specialized structure which is intended to hold reusable metadata outside of the structures of a single StudyUnit or Group. For example this may be common methodological approaches bound in a DataCollection module, DataRelationship information bound in a LogicalProduct, or any maintainable scheme. The ResourcePackage is often used to manage and publish metadata that is used by StudyUnits or Groups by reference. Any maintainable object with the exception of a Group, StudyUnit or LocalHoldingPackage may be published in a Resource Package. Each maintainable object may be entered as either an in-line representation or by reference. Within each maintainable type the ordering of in-line or referenced content may be mixed. In addition the ResourcePackage contains self identifying information includin a citation, abstract, authorization source, a universe reference, series statement, references to applicable quality statements, funding and budget information, purpose, coverage, other material, embargo, and the resource package archive (as opposed to an Archive module intended as the part of the published reusable content).

Property: 
NameCardinalityDatatypeDescription
Citation
0..1
The citation for the ResourcePackage. DDI strongly recommends that at minimum a Title be provided.
TypeOfResourcePackage
0..1
A brief description of the resource package type. Supports the use of a controlled vocabulary.
Abstract
0..1
An abstract of the ResourcePackage unit describing the nature and scope of the data collection, special characteristics of its content. Note that detailed information on the purpose of the ResourcePackage 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 ResourcePackage, why the ResourcePackage took place. This should include detailed information on the investigator's primary ResourcePackage 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.
OtherMaterial
0..n
Contains references to other materials relevant to the ResourcePackage 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.
Relationship: 
NameTarget ObjectDescriptionSource cardinalityTarget cardinalityRelationship type
AuthorizationSource
Identifies the authorizing agency for the ResourcePackage 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
UniverseReference
Reference to the universe statement from the universe scheme, describing the ResourcePackage 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 ResourcePackage. A universe may be described as "inclusive" or "exclusive". This ResourcePackage level reference is normally to the top level of the UniverseScheme.
0..1
SeriesStatement
A ResourcePackage, particularly one in a series, may be the result of two series merging into a single ResourcePackage. The new ResourcePackage 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
QualityStatementReference
A reference to a QualityStatementScheme containing statements of quality related to the quality of the ResourcePackage methodology, metadata, or data. Quality statements may be related to external quality standards.
0..n
FundingInformation
Contains details of the ResourcePackage unit's funding, including information about grants, agencies, etc.
0..n
ProjectBudget
This describes the overall budget of the ResourcePackage. 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
Coverage
Describes the coverage of the ResourcePackage 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
Embargo
Embargo information about the ResourcePackage unit. References to embargo information in this section can be made from individual variables.
0..n
ResourcePackageArchive
This is archive information specific to the creation, maintenance, and archiving of the ResourcePackage provided either in-line or by reference. This packaging element differentiates this "Archive" from one being published as a product within a ResourcePackage.
0..n
ConceptualComponent
Allows for in-line entry of an ConceptualComponent.
0..n
DataCollection
Allows for in-line entry of an DataCollection.
0..n
BaseLogicalProduct
Allows for in-line entry of any LogicalProduct. BaseLogicalProduct is a substitution group base.
0..n
PhysicalDataProduct
Allows for in-line entry of an PhysicalDataProduct.
0..n
PhysicalInstance
Allows for in-line entry of an PhysicalInstance.
0..n
Archive
Allows for in-line entry of an Archive.
0..n
DDIProfile
Allows for in-line entry of an DDIProfile.
0..n
Comparison
Allows for in-line entry of an Comparison.
0..n
OrganizationScheme
In-line inclusion of a OrganizationScheme.
0..n
ConceptScheme
In-line inclusion of a ConceptScheme.
0..n
UniverseScheme
In-line inclusion of a UniverseScheme.
0..n
ConceptualVariableScheme
In-line inclusion of a ConceptualVariableScheme.
0..n
RepresentedVariableScheme
In-line inclusion of a RepresentedVariableScheme.
0..n
GeographicStructureScheme
In-line inclusion of a GeographicStructureScheme.
0..n
GeographicLocationScheme
In-line inclusion of a GeographicLocationScheme.
0..n
InterviewerInstructionScheme
In-line inclusion of a InterviewerInstructionScheme.
0..n
ControlConstructScheme
In-line inclusion of a ControlConstructScheme.
0..n
QuestionScheme
In-line inclusion of a QuestionScheme.
0..n
CategoryScheme
In-line inclusion of a CategoryScheme.
0..n
CodeListScheme
In-line inclusion of a CodeListScheme.
0..n
NCubeScheme
In-line inclusion of a NCubeScheme.
0..n
VariableScheme
In-line inclusion of a VariableScheme.
0..n
PhysicalStructureScheme
In-line inclusion of a PhysicalStructureScheme.
0..n
RecordLayoutScheme
In-line inclusion of a RecordLayoutScheme.
0..n
QualityStatementScheme
In-line inclusion of a QualityStatementScheme.
0..n
InstrumentScheme
In-line inclusion of a InstrumentScheme.
0..n
ProcessingEventScheme
In-line inclusion of a ProcessingEventScheme.
0..n
ProcessingInstructionScheme
In-line inclusion of a ProcessingInstructionScheme.
0..n
ManagedRepresentationScheme
In-line inclusion of a ManagedRepresentationScheme.
0..n

Stage:

DDI 3.2: 
g:ResourcePackageType
Is extendable: 
RDF Mapping: