About Derived Name and Address Attributes - trillium_discovery - trillium_quality - 17.1

Trillium Control Center

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Discovery
Trillium > Trillium Quality
Version
17.1
Language
English
Product name
Trillium Quality and Discovery
Title
Trillium Control Center
Topic type
Administration
Overview
How Do I
Configuration
Reference
Installation
First publish date
2008

When passing data between Trillium (Trillium) and client applications, it is useful to have one set of Trillium attribute names to map to the client application’s attributes, regardless of the data’s country of origin. For example, to pass a street name from Trillium to a client application, you would want to map one "STREET_NAME" Trillium attribute to one client attribute.

In a multi-country project, this can be complicated by the different attribute names and structure of address information for different countries. For example, the following is street information for three countries as it would be stored in the repository after being processed by the Postal Matcher:

  • For the United Kingdom:

GB_GOUT_THOROUGH_NAME and GB_GOUT_THOROUGH_DESC

  • For Canada:

CA_GOUT_STREET_NAME and CA_GOUT_STREET_TYPE

  • For the United States:

US_GOUT_STREET_PRE_DIRECTION, US_GOUT_STREET_NAME,

US_GOUT_STREET_SUFFIX, and US_GOUT_STREET_POST_DIRECTION

To simplify mapping Trillium attributes into client applications, Trillium constructs a set of derived attributes to store address information. The Transformer Data Reconstruction in each country template determines the value of the derived attributes based on the addressing standards for that country.

Following the above example, for data being processed through the GB country template the GB Transformer Data Reconstruction would derive the value of dr_street_name by combining two GB-specific attributes:

SET dr_street_name = GB_GOUT_THOROUGH_NAME |: GB_GOUT_THOROUGH_DESC

Dr_street_name would then contain street information appropriate for the United Kingdom, and that value can then be passed to a client application.

Derived Attributes

The following derived attributes are included in all country templates. Their values are determined by the country’s Transformer Data Reconstruction process. To view the definition of a country’s derived attributes, examine the country’s Transformer Data Reconstruction settings file (for example, for the United Kingdom, examine GBdrtrans.stx).

dr_Address

dr_Address_2

dr_Alias Account

dr_Alias Contact

dr_Business Name

dr_City Name

dr_Country Code

dr_Country Name (Note: This is not equivalent to dr_country, described below.)

dr_First Name

dr_House Number1

dr_House Number2

dr_Last Name

dr_Middle Name

dr_Mrmrs

dr_Neighborhood

dr_Neighborhood_2

dr_Postal Code

dr_Project Code

dr_Region Name

dr_Street Name

The dr_project_code Attribute

Dr_project_code contains a two-character country code of the country template. This attribute is useful in the following cases:

Case 1: It helps to flag and group the ZZ (basic) countries later in the project flow. For example, if you have a multi-country project including Egypt and Iran (ZZ countries), the value of the Save Country attribute from the Global Data Router will be EG and IR, respectively. But dr_project_code remains ZZ for both and you can group them as coming from the ZZ country group.

Case 2: It helps to identify the project flow when you route a country to another country. For example, if you routed Canadian (CA) data to US, the dr_project_code will be US. But you can manually change the dr_country_code from US to the value of the Save Country attribute from the Router to indicate whether it is actually a US or a CA data.

The dr_country Attribute

Dr_country is also a derived attribute, but it is unique. Unlike other derived attributes, dr_country is not included in the input or output schema of any process step. It is constructed internally to store a two-character country code derived from project data. This country code is required for real-time projects.

Note: Do not modify settings or schema files to include an attribute named dr_country. Overwriting dr_country may impact processing of real-time projects.