Custom properties created when reading from Triple-S files
When the Triple-S DSC uses a Triple-S metadata file to read a Triple-S case data file, it creates custom properties in the generated UNICOM Intelligence Metadata Model (MDM) document to store additional information about the format of the Triple-S data.
If the generated MDM document is used to create further Triple-S files, many of these custom properties define the content of those files. For more information, see
Custom properties used when writing to Triple-S files.
The Triple-S DSC creates a user context to store many of the custom properties. The actual user context that it creates depends on the value of the format attribute (if specified) in the Triple-S metadata file’s <record> element, as follows:
|
Value of format attribute
|
Implied format of Triple-S case data
|
User context created
|
|
"fixed", or if format attribute not specified
|
Fixed-format fields
|
CARDCOL
|
|
"csv"
|
Comma-separated values
|
CSV
|
For those custom properties that are created in the CARDCOL user context, the Triple-S DSC always stores the custom properties in the DataSourceProperties collection for the mrPunchDsc DataSource object. For those custom properties that are created in the CSV user context, the Triple-S DSC always stores the custom properties in the DataSourceProperties collection for the mrCsvDsc DataSource object.
The Triple-S DSC also creates some custom properties in the Analysis user context, regardless of the implied format of the Triple-S case data. The Triple-S DSC also stores some of these custom properties in the DataSourceProperties collection for the mrPunchDsc or mrCsvDsc DataSource object, depending on the implied format of the Triple-S case data.
See also
‘Custom properties on elements’ on page 600
Custom properties on the Document object
The Triple-S DSC adds the following custom properties to the MDM Document object:
ident
Value: The value of the ident attribute in the Triple-S metadata file's <record> element.
User context: CARDCOL or CSV, depending on the implied format of the Triple-S case data.
SerialFullName
Value: The name of the MDM variable that corresponds to the Triple-S variable that has a use="serial" attribute setting.
User context: CARDCOL or CSV, depending on the implied format of the Triple-S case data.
Skip
Value: The value of the skip attribute in the Triple-S metadata file's <record> element.
User context: CARDCOL or CSV, depending on the implied format of the Triple-S case data.
SssDate
Value: The value of the <date> element in the Triple-S metadata file.
User context: Analysis.
SssFormat
Value: Either "fixed" or "csv", depending on the implied format of the Triple-S case data.
User context: Analysis. If the implied format of the Triple-S case data is fixed-format fields, the Triple-S DSC stores SssFormat in the DataSourceProperties collection for the mrPunchDsc DataSource object. If the implied format of the Triple-S case data is comma-separated values, the Triple-S DSC stores SssFormat in the DataSourceProperties collection for the mrCsvDsc DataSource object.
SssOrigin
Value: The value of the <origin> element in the Triple-S metadata file.
User context: Analysis.
SssSurveyName
Value: The value of the <name> element in the Triple-S metadata's <survey> element.
User context: Analysis.
SssTime
Value: The value of the <time> element in the Triple-S metadata file.
User context: Analysis.
SssUser
Value: The value of the <user> element in the Triple-S metadata file.
User context: Analysis.
SssVersion
Value: The value of the version attribute in the Triple-S metadata file's <sss> element. Note that the Triple-S DSC issues an error message if the value of the version attribute is not "1.2" or "2.0".
User context: Analysis.
See also