The staged schema is a separate set of database tables with a portion of the data from the TCA Registry that transformations have standardized for improved matching. During matching, the input record is compared against the records in the staged schema instead of the original Registry. To enable efficient searches, the staged schema is indexed using Oracle interMedia and B-Tree indexes. DQM searches against the indexes to take advantage of high performance capabilities in searching through large quantities of data.
Each table in the staged schema contains attribute values for each entity: Party, Address, Contact, and Contact Point, and can include up to 30 custom attributes. In the Define Attributes and Transformations page, you define the attributes that you want in the staged schema as well as the transformations to apply to each attribute value. See: Defining Attributes and Transformations.
For example, for the Party entity, you can include the party name attribute and specify two transformations to transform the party names. Each attribute, in essence, corresponds to a column in a TCA Registry table that stores the attribute value, and the staged schema contains the transformed version of those values.
See: Seeded Attributes, Oracle Trading Community Architecture Reference Guide.
This table shows the mapping of the TCA Registry to the staged schema. The staged schema table that is used depends on the program you run to stage data. See: Administering the Staged Schema.
| Entity | TCA Registry Table | Staged Schema Table |
|---|---|---|
| Party | HZ_PARTIES | HZ_STAGED_PARTIES |
| Address | HZ_PARTY_SITES HZ_STAGED_PARTY_SITES_SHADOW | HZ_STAGED_PARTY_SITES |
| Contact | HZ_ORG_CONTACTS | HZ_STAGED_CONTACTS |
| Contact Point | HZ_CONTACT_POINTS | HZ_STAGED_CONTACT_POINTS |
Data Quality Management lets you:
Create and update the staged schema. See: DQM Staging Program.
Synchronize the staged schema with the TCA Registry. See: DQM Synchronization Method.
interMedia indexes speed up the acquisition phase of the matching process by quickly limiting the number of parties to evaluate for scoring. interMedia indexes are built using inverted indexes, a structure that differs from normal indexes. DQM provides four interMedia indexes, one for each entity.
You can:
Create and update interMedia indexes. See: DQM Staging Program.
Optimize interMedia indexes. See: DQM Index Optimization Program.
Synchronize interMedia indexes with TCA Registry data. See: DQM Synchronization Method.
B-Tree indexes are created in the staged schema only for attributes that were transformed for bulk duplicate identification. These indexes provide increased performance over interMedia indexes, and are used only for matching processes that involve match rules with the Bulk Duplicate Identification purpose. See: Bulk Duplicate Identification.
You can:
Create and update B-Tree indexes. See: DQM Staging Program.
Synchronize B-Tree indexes with TCA Registry data. See: DQM Synchronization Method.