Real Time Information Director User Documentation

RTID Metadata Language
Hewlett-Packard Company 51 529618-002
Common Characteristics of Variant, Aliased and Substitute
Documents
Although variant, aliased, and substitute document definitions serve different purposes,
they have some important characteristics in common.
One is that the same SQL statements generated for the base document are used for the
related variant, aliased, or substitute documents. This behavior saves SQL compilation
time, conserves SQL connections, and lets you deploy new format metadata without
recompiling SQL statements.
Another common characteristic is dynamic deployment. A management interface
(described in the document called RTID Management) notifies a running system when a
new document class is available, whether that class is a replacement or a completely new
document definition.
Considerations for Mapping IDoc Tags
Here are a few final considerations for mapping IDoc tags:
• In a document definition, include all tags to be mapped to the data store. If a tag
doesn’t need to be mapped, don’t include it in the metadata.
• Tags that you define will be recognized in inbound documents, even if you
neglect to map the segment under which that tag is nested in the inbound
document.
• The order that you specify the tags does not matter when loading inbound
documents. In outbound documents, tags will occur in the order in which you
listed them in the metadata.
Enriching the Data
Enrichments are polymorphic objects that can be specified in various combinations
within any level of the content metadata. That is, enrichments can be applied to the
DocumentRecord (the top record in a document) or to any RelatedRecords (nested
records in a document).
It is also possible to apply multiple enrichments to the same document or record. One
way to do this is to specify a compound enrichment followed by a bracketed list of
enrichments. (See the Javadoc for CompoundEnrichment.) A better way is to define an
enriched record, passing an array of enrichments to the EnrichedRecord class, as in the
following example:
public static final EnrichedRecord joinedCheckoutItem =
Library.aliasedCheckoutRecord.enrich(new Enrichment[] {