Configuring the Matching Service for Address Data (Repository)
To ensure the master index application uses the Sun Match Engine to process address information, you must customize the Matching Service. This includes modifying the Match Field file to support the fields on which you want to match, to standardize the appropriate fields, and to specify the Sun Match Engine as the match and standardization engine (by default, the Sun Match Engine is already specified so this does not need to be changed). Perform the following tasks to configure the Matching Service.
When configuring the Matching Service, keep in mind the information presented in Configuring the Master Index Matching Service (Repository).
Configuring the Standardization Structure for Address Data (Repository)
The standardization structure is configured in the StandardizationConfig section of the Match Field file, which is described in detail in Match Field Configuration (Repository) in Understanding Sun Master Index Configuration Options (Repository). To configure the required fields for standardization and phonetic encoding, modify the standardization and phonetic encoding structures. The following sections provide additional guidelines and samples specific to standardizing address data.
Note –
In the default configuration, the rules defined for the address data type assume that all input fields must be parsed as well as normalized. Thus, there is no need to configure fields only for normalization.
Address Standardization Structures
For address fields, the source fields in the standardization structure must include the fields predefined for parsing and normalization. This includes any fields containing street address information, which are parsed into the street address fields listed in Address Data Object Structure (excluding the phonetic street name field). The target fields can include any of these parsed fields. Follow the instructions under Defining Master Index Standardization Rules (Repository) in Configuring Sun Master Indexes (Repository) to define fields for normalization. For the standardization-type element, enter Address (for more information, see Sun Match Engine Match and Standardization Types). For a list of field IDs to use in the standardized-object-field-id element, see Table 3.
A sample standardization structure for address data is shown below. This structure parses the first two lines of street address into the standard street address fields. Only the United States domain is defined in this structure.
free-form-texts-to-standardize>
<group standardization-type="ADDRESS"
domain-selector="com.stc.eindex.matching.impl.SingleDomainSelectorUS">
<unstandardized-source-fields>
<unstandardized-source-field-name>Person.Address[*].Address1
</unstandardized-source-field-name>
<unstandardized-source-field-name>Person.Address[*].Address2
</unstandardized-source-field-name>
</unstandardized-source-fields>
<standardization-targets>
<target-mapping>
<standardized-object-field-id>HouseNumber
</standardized-object-field-id>
<standardized-target-field-name>Person.Address[*].HouseNumber
</standardized-target-field-name>
</target-mapping>
<target-mapping>
<standardized-object-field-id>RuralRouteIdentif
</standardized-object-field-id>
<standardized-target-field-name>Person.Address[*].HouseNumber
</standardized-target-field-name>
</target-mapping>
<target-mapping>
<standardized-object-field-id>BoxIdentif
</standardized-object-field-id>
<standardized-target-field-name>Person.Address[*].HouseNumber
</standardized-target-field-name>
</target-mapping>
<target-mapping>
<standardized-object-field-id>MatchStreetName
</standardized-object-field-id>
<standardized-target-field-name>Person.Address[*].StreetName
</standardized-target-field-name>
</target-mapping>
<target-mapping>
<standardized-object-field-id>RuralRouteDescript
</standardized-object-field-id>
<standardized-target-field-name>Person.Address[*].StreetName
</standardized-target-field-name>
</target-mapping>
<target-mapping>
<standardized-object-field-id>BoxDescript
</standardized-object-field-id>
<standardized-target-field-name>Person.Address[*].StreetName
</standardized-target-field-name>
</target-mapping>
<target-mapping>
<standardized-object-field-id>PropDesPrefDirection
</standardized-object-field-id>
<standardized-target-field-name>Person.Address[*].StreetDir
</standardized-target-field-name>
</target-mapping>
<target-mapping>
<standardized-object-field-id>PropDesSufDirection
</standardized-object-field-id>
<standardized-target-field-name>Person.Address[*].StreetDir
</standardized-target-field-name>
</target-mapping>
<target-mapping>
<standardized-object-field-id>StreetNameSufType
</standardized-object-field-id>
<standardized-target-field-name>Person.Address[*].StreetType
</standardized-target-field-name>
</target-mapping>
<target-mapping>
<standardized-object-field-id>StreetNamePrefType
</standardized-object-field-id>
<standardized-target-field-name>Person.Address[*].StreetType
</standardized-target-field-name>
</target-mapping>
</standardization-targets>
</group>
</free-form-texts-to-standardize>
|
Address Phonetic Encoding
When you match or standardize on street address fields, the street name should be specified for phonetic conversion (this is done by default). Follow the instructions under Defining Phonetic Encoding for the Master Index (Repository) in Configuring Sun Master Indexes (Repository) to define fields for phonetic encoding.
A sample of the phoneticize-fields element is shown below. This sample only converts the address street name. You can define additional fields for phonetic encoding.
<phoneticize-fields>
<phoneticize-field>
<unphoneticized-source-field-name>Person.Address[*].StreetName
</unphoneticized-source-field-name>
<phoneticized-target-field-name>Person.Address[*].StreetName_Phon
</phoneticized-target-field-name>
<encoding-type>NYSIIS</encoding-type>
</phoneticize-field>
</phoneticize-fields>
|
Configuring the Match String for Address Data (Repository)
For matching on street address fields, make sure the match string you specify in the MatchingConfig section of the Match Field file contains all or a subset of the fields that contain the standardized data (the original text in street address fields are generally too inconsistent to use for matching). You can include additional fields for matching, such as the city name or postal code.
To configure the match string, follow the instructions under Defining the Master Index Match String (Repository) in Configuring Sun Master Indexes (Repository). For the Sun Match Engine, each component of a street address has a different match type (specified by the match-type element). The default match types for addresses are StreetName, HouseNumber, StreetDir, and StreetType. You can specify any of the other match types defined in the match configuration file, as well. For more information, see Sun Match Engine Match and Standardization Types.
A sample match string for address matching is shown below.
<match-system-object>
<object-name>Person</object-name>
<match-columns>
<match-column>
<column-name>Enterprise.SystemSBR.Person.Address.StreetName
</column-name>
<match-type>StreetName</match-type>
</match-column>
<match-column>
<column-name>Enterprise.SystemSBR.Person.Address.HouseNumber
</column-name>
<match-type>HouseNumber</match-type>
</match-column>
<match-column>
<column-name>Enterprise.SystemSBR.Person.Address.StreetDir
</column-name>
<match-type>StreetDir</match-type>
</match-column>
<match-column>
<column-name>Enterprise.SystemSBR.Person.Address.StreetType
</column-name>
<match-type>StreetType</match-type>
</match-column>
</match-columns>
</match-system-object>
|
- © 2010, Oracle Corporation and/or its affiliates