Configuring the Matching Rules
You can define one or more matching rules for an index in the matching rules file. You can define the matching rules within the
To define a matching rule, add the following parameters to the
section within the
- Includes a matching rule and and its properties. Use multiple
MatchConfiguration sections within the
MatchRuleSet section to configure multiple rules.
- You can set the following properties for a matching rule:
- MatchRuleID. Unique name for the match rule. The name cannot exceed 14 characters.
- AutoMergeInd. Indicates whether to merge the matching records manually or automatically. Set to Yes for automatic merging, and set to No for manual merging.
- Type of purpose that you want to use for matching. You can use one of the following standard SSA-NAME3 purposes:
- Address. Identifies an address match.
- Contact. Identifies a contact within an organization at a specific location.
- Division. Identifies an organization at an address.
- Fields. Identifies generic data.
- Household. Identifies individuals with same or similar family names who share the same address.
- Individual. Identifies a specific individual by name, ID, or date of birth.
- Organization. Identifies an organization by name.
- Person_Name. Identifies a person by name.
- Resident. Identifies a person at an address.
- Wide_Contact. Identifies a contact within an organization.
- Optional. Level of matching that you want to perform. Use one of the following values:
- Typical. Returns more results that the conservative match level and less results than the loose match level.
- Conservative. Returns almost accurate results, and you can use in environments where the accuracy of a match is important.
- Loose. Returns matches with more variations than typical match, and you can use in environments where you can manually review the results.
Default is Typical.
- Minimum score that SSA-NAME3 requires to consider a record as a matching candidate.
- Maps the SSA-NAME3 fields with the input record fields and sets the properties for each field. You can set the following properties for each field:
- name. Indicates the SSA-NAME3 field for the input record field.
- type. Indicates the type of matching to perform on the field. Set to Fuzzy to perform fuzzy matching, and set to Exact to perform exact matching on the field values.
- segment_ind. Optional. Indicates whether you want to enable segment matching. Set to 1 to enable segment matching and 0 to disable segment matching. Default is 0.
- segment_val. Optional. Indicates the value based on which you want to perform segment matching. Specify the
segment_val parameter only when you enable segment matching.
- null_ind. Optional. Indicates how to handle null values during the matching process. Set to 0 if you do not want to match a null value against any value. Set to 1 to consider two null values as a match. Set to 2 to consider a null value and a non-null value as a match. Default is 0.
- anti_ind. Optional. Indicates whether you want to perform non-equal matching. A non-equal matching returns a successful match only when the records do not match. Set to 1 to enable non-equal matching and set to 0 to disable non-equal matching. Default is 0.
- Optional. Additional attributes that you want to specify. You can specify the following attributes:
- NAMEFORMAT=L|R. Indicates whether the major word in a name or address is on the left end or the right end. For example, in Western names, the family name is on the right end of the names.
- UNICODE_ENCODING. Specifies the Unicode format of the data that you use.
You can define additional
MatchConfiguration sections within the
MatchRuleSet section to define multiple matching rules.
The following sample shows a matching rule definition named Rule1:
<MatchConfiguration MatchRuleID="Rule1" AutoMergeInd="yes">
<MField name="SSN_Ex" type="Exact" segment_ind="1" segment_val="M" null_ind="2" anti_ind="0">PersonSSN</MField>
<MField name="Person_Name2" type="Fuzzy" segment_ind="0" null_ind="0" anti_ind="0">PersonFirstName</MField>
<MField name="Person_Name3" type="Fuzzy" segment_ind="0" null_ind="0" anti_ind="0">PersonLastName</MField>
<MField name="Address_Part1" type="Fuzzy" segment_ind="0" null_ind="0" anti_ind="0">ShippingAddress</MField>
<MField name="Zipcode_Ex" type="Exact" segment_ind="0" null_ind="0" anti_ind="0">ShippingPostalCode</MField>