complexType "LogicalRecordType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
|
Used: |
|
XML Representation Summary |
<... |
|
|
= |
("Add" | "Update" | "Delete") |
|
= |
(xs:string | xs:string) |
|
= |
("Agency" | "Maintainable") : "Agency" |
|
= |
xs:boolean |
|
= |
"true" |
|
= |
xs:boolean |
|
= |
xs:integer |
|
|
> |
|
Content: |
(r:URN | (r:Agency, r:ID, r:Version))[1..2], r:UserID*, r:MaintainableObject?, LogicalRecordName*, r:Label*, r:Description?, VariableValueReference?, SupportForMultipleSegments?, CaseIdentification*, (VariablesInRecord | NCubesInRecord)?, DefaultMissingValues? |
|
</...> |
Content Model Elements (15):
-
CaseIdentification,
DefaultMissingValues,
LogicalRecordName,
NCubesInRecord,
SupportForMultipleSegments,
VariableValueReference,
VariablesInRecord,
r:Agency,
r:Description,
r:ID,
r:Label,
r:MaintainableObject,
r:URN,
r:UserID,
r:Version
All Direct / Indirect Based Elements (1):
-
Annotation
A logical record is a description of all of the elements (variables or NCubes) related to a single case or analysis unit. Required to link a description of a physical record structure to its logical record. In addition to the standard name, label, and description, the structure identifies the variable designating its record type, describes case identification within the record type, indicates support for multiple storage segments, and defines a default set of missing values used by the record. In a data set with multiple records repeat to describe each logical record, such as a household, family, person, or event, record. A LogicalRecord is required to link a description of a physical record structure to its logical record.
Type Derivation Tree
LogicalRecordType
|
XML Source (w/o annotations (12); see within schema source)
<xs:complexContent>
<xs:extension base="r:IdentifiableType">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="LogicalRecordName"/>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="r:Label"/>
<xs:choice minOccurs="0">
</xs:choice>
</xs:sequence>
<xs:attribute name="hasLocator" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
|
Attribute Detail (all declarations; defined within this component only; 2/7)
hasLocator
-
Type: |
xs:boolean, predefined |
Use: |
optional |
If "true" indicates that the record type has a field which identifies its record type. In logical structures with a single record type there is generally no identifier. Most multi-record files will have a variable that identifies the record type.
XML Source (w/o annotations (1); see within schema source)
<xs:attribute name="hasLocator" type="xs:boolean" use="optional"/>
|
variableQuantity
-
Type: |
xs:integer, predefined |
Use: |
optional |
Number of variables in the logical record. Caution in using optional checksums is recommended. Conflict between checksums and the items being counted can cause problems with warning flags during processing. If using checksum to capture information for internal processing purposes, the use of automatically generated check sums is strongly urged.
XML Source (w/o annotations (1); see within schema source)
Content Element Detail (all declarations; defined within this component only; 9/15)
-
Describes the information needed to identify an individual case within a record type. This may be the variable or concatenated variable used to identify a unique case of a particular record type. Often referred to as a unique key. There may be more than one means of identifying a record. For example a US Census Summary File has a LogicalRecordIdentifier that is unique to the original file within which it was published. A specific geography has a set of fields that uniquely identify it.
XML Source (w/o annotations (1); see within schema source)
-
Identifies the default missing value parameter for the this logical record by referencing a ManagedMissingValuesRepresentation or by stating that there is a default missing values parameter used but it is undocumented. Note that a conflicting DefaultMissingValues definition in a PhysicalInstance will override that found in the LogicalRecord.
XML Source (w/o annotations (1); see within schema source)
-
A name for the LogicalRecord. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.
XML Source (w/o annotations (1); see within schema source)
-
List of all NCubes used in the record, either directly or as found in a defined NCubeGroup; note that an NCube can be used in multiple records. The NCubes in the logical record can be noted by inclusion or exclusion to facilitate listing. The attribute allNCubesInLogicalProduct, when set to 'true', includes all NCubes in the LogicalProduct. NCubeSchemeReference can then be used to exclude individual NCubes schemes or include schemes from other logical products. In the same way NCubeReference can be used to exclude specific variables from the previously defined variable set or include variables not already included. The simplest LogicalProduct descriptions with a single LogicalRecord can be described using only the attribute allNCubesInLogicalProduct with a value of true.
XML Source (w/o annotations (1); see within schema source)
-
A description of the content and purpose of the LogicalRecord. May be expressed in multiple languages and supports the use of structured content.
XML Source (w/o annotations (1); see within schema source)
-
A display label for the LogicalRecord. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" ref="r:Label"/>
|
-
Information concerning support for breaking the logical record into segments for storage purposes. Some files may be broken into record segments for storage but lack variables to support identification of specific segments. In this case segments are identified by their physical order within the storage file.
XML Source (w/o annotations (1); see within schema source)
-
List of all variables used in the record, either directly or as found in a defined VariableGroup; note that a variable can be used in multiple records. The variables in the logical record can be noted by inclusion or exclusion to facilitate listing. The attribute allVariablesInLogicalProduct, when set to 'true', includes all variables in the LogicalProduct. VariableSchemeReference can then be used to exclude individual Variables schemes or include schemes from other logical products. In the same way VariableReference can be used to exclude specific variables from the previously defined variable set or include variables not already included. The simplest LogicalProduct descriptions with a single LogicalRecord can be described using only the attribute allVariablesInLogicalProduct with a value of true.
XML Source (w/o annotations (1); see within schema source)
-
A reference the variable containing the record type locator and the value being used. Files with single record types or which store records in different files may not have a record type locator. If this element is used set the attribute hasLocator to "true".
XML Source (w/o annotations (1); see within schema source)