PhysicalInstanceOLD

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

Includes information about the physical instance of a data product (an actual data file). It completes the documentation contained in the Physical Data Product module that is specific to the individual file and serves as a descriptive record of the external data file. Physical Instance provides a citation for the data file, a link to the RecordLayout(s) used by the files records, a description of it coverage (as a constraint if different from the study), check figures for quality control (e.g. digital fingerprint, record count, etc.), and a statistical summary of the data in the file at both the variable and category level.

Property: 
NameCardinalityDatatypeDescription
citation
0..1
A citation for the physical instance of a data set. Note that a DOI or similar unique identifier for the data file should be placed in InternationalIdentifier. It is strongly recommended that use of a Citation in this location includes the use of the optional sub-element Title.
proprietaryInfo
0..1
Contains information proprietary to the software package which produced the data file. This is expressed as a set of name-value pairs. The value may be taken from a controlled vocabulary.
byteOrder
0..1
Contains a term from a controlled vocabulary indicating the byte ordering.
Relationship: 
NameTarget ObjectDescriptionSource cardinalityTarget cardinalityRelationship type
dataFingerprint
Allows for assigning a hash value (digital fingerprint) to the data or data file. Set the attribute flag to "data" when the hash value provides a digital fingerprint to the data contained in the file regardless of the storage format (ASCII, SAS, binary, etc.). One approach to compute a data fingerprint is the Universal Numerical Fingerprint (UNF). Set the attribute flag to "dataFile" if the digital fingerprint is only for the data file in its current storage format.
0..1
0..n
Neither
coverage
Includes information about the topical, spatial, and temporal coverage of the physical instance. May be expressed as a restriction of the parent study coverage.
0..1
0..1
Neither
dataRelationshipReference
Reference to the DataRelationship containing the LogicalRecord to which the RecordLayout refers. Repeat for cases where LogicalRecords are described in multiple DataRelationship structures. Note that this does not imply that all of the LogicalRecords described in the DataRelationship are contained, wholly or in part in the PhysicalInstance. This reference allows for a direct path between the PhysicalInstance and the related content found in a LogicalProduct.
0..1
0..n
Neither
recordLayoutReference
References the record layout of the data documented in the physical instance.
0..1
0..n
Neither
defaultMissingValuesReference
References the content of the default missing values used in the file. The content of this file overrides default missing value information provided in the LogicalRecord. Allows for the specification that is a Systems Missing Value.
0..1
0..1
Neither
dataFileIdentification
Identifies the data file documented in the physical instance and provides information about its location.
0..1
0..n
Neither
dataFileVersion
Provides the version information for the data file related to this physical instance. Note that while Physical Instance allows for multiple copies of the same data file (such as backup copies) the assumption is that they are identical in terms of content, layout, format and version.
0..1
0..1
Neither
qualityStatementReference
A reference to a Quality Statement pertaining to the quality of the study methodology, metadata, or data to which it is associated. Quality statements may be related to external quality standards.
0..1
0..n
Neither
grossFileStructure
Includes information about the file structure, as well as other characteristics that are specific to the physical instance.
0..1
0..1
Neither
statisticalSummary
Includes variable and category statistics data documented in the physical instance, or a reference to a physical instance where the statistics are described or located in line.
0..1
0..1
Neither
otherMaterial
Description and link to an external non-DDI object.
0..n
0..n
Neither

Stage:

DDI 3.2: 
pi:PhysicalInstanceType
Is extendable: 
Is property: 
0
RDF Mapping: 

Comments

This or another element is needed by SimpleCodebook to have sub-elements like OtherMaterial, StatisticalSummary etc.