Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

List of Match Purposes

List of Match Purposes

 The following table describes match purposes that
Informatica
provides:
Match Purpose
Description
Person_Name
Identifies a person by name. Use the purpose for online searches when a name-only lookup is required and a human is available to make the choice. Matching requires other attributes in addition to name to make match decisions. When you use this purpose, the rule must not contain address fields. This purpose matches people with an address and those without an address. If the rules contain address fields, use the Resident purpose instead.
This purpose uses the following fields:
  • Person_Name (Required)
  • Address_Part1
  • Address_Part2
  • Postal_Area
  • Telephone_Number
  • ID
  • Date
  • Attribute1
  • Attribute2
  • Geocode
To achieve a best of score between Address_Part2 and Postal_Area, use Postal_Area as a repeat value in the Address_Part2 field.
Individual
Identifies an individual by the name, ID number, and date of birth attributes.
Use the Individual match purpose after a search by Person_Name as this match purpose requires additional information that the Person_Name match purpose provides.
This match purpose uses the following fields:
  • Person_Name (Required)
  • ID (Required)
  • Date (Required)
  • Attribute1
  • Attribute2
Resident
Identifies a person at an address. Use this match purpose after a search by either Person_Name or Address_Part1. Optional input fields help qualify or rank a match if more information is available.
To achieve a best of score between Address_Part2 and Postal_Area, pass Postal_Area as a repeat value in the Address_Part2 field.
This match purpose uses the following fields:
  • Person_Name (Required)
  • Address_Part1 (Required)
  • Address_Part2
  • Postal_Area
  • Telephone_Number
  • ID
  • Date
  • Attribute1
  • Attribute2
  • Geocode
Household
Identifies matches where individuals with the same or similar family names share the same address.
Use this match purpose after a search by Address_Part1.
A search by Person_Name is not practical because ultimately one word from the Person_Name must match, and a one-word search is not effective in most situations.
Emphasis is on the Last Name, the major word of the Person_Name field, so this is one of the few cases where word order is important in the way the records are presented for matching.
However, a reasonable score is generated, provided that a match occurs between the major word in one name and any other word in the other name.
This match purpose uses the following fields:
  • Person_Name (Required)
  • Address_Part1 (Required)
  • Address_Part2
  • Postal_Area
  • Telephone_Number
  • Attribute1
  • Attribute2
  • Geocode
To achieve a best of score between Address_Part2 and Postal_Area, pass Postal_Area as a repeat value in the Address_Part2 field.
Family
Identifies matches where individuals with the same or similar family names share the same address or the same telephone number.
Use this match purpose after a tiered search (multisearch) by Address_Part1 and Telephone_Number.
A search by Person_Name is not practical because ultimately one word from the Person_Name must match, and a one-word search is not effective in most situations.
Emphasis is on the Last Name, the major word of the Person_Name field, so this is one of the few cases where word order is important in the way the records are presented for matching.
However, a reasonable score is generated provided that a match occurs between the major word in one name and any other word in the other name.
This match purpose uses the following fields:
  • Person_Name (Required)
  • Address_Part1 (Required)
  • Telephone_Number (Required) (Score is based on best of Address_Part_1 and Telephone_Number)
  • Address_Part2
  • Postal_Area
  • Attribute1
  • Attribute2
  • Geocode
To achieve a best of score between Address_Part2 and Postal_Area, pass Postal_Area as a repeat value in the Address_Part2 field.
Wide_Household
Identifies matches where the same address is shared by individuals with the same family name or with the same telephone number.
Use this match purpose after a search by Address_Part1.
A search by Person_Name is not practical because ultimately one word from the Person_Name must match, and a one-word search is not effective in most situations.
Emphasis is on the last name, the major word of the Person_Name field, so this is one of the few cases where word order is important in the way the records are presented for matching.
However, a reasonable score is generated provided that a match occurs between the major word in one name and any other word in the other name.
This match purpose uses the following fields:
  • Address_Part1 (Required)
  • Person_Name (Required)
  • Telephone_Number (Required) (Score is based on best of Person_Name and Telephone_Number)
  • Address_Part2
  • Postal_Area
  • Attribute1
  • Attribute2
  • Geocode
To achieve a best of score between Address_Part2 and Postal_Area, pass Postal_Area as a repeat value in the Address_Part2 field.
Address
Identifies an address match. The address might be postal, residential, delivery, descriptive, formal, or informal.
The required field is Address_Part1. The fields Address_Part2, Postal_Area, Telephone_Number, ID, Date, Attribute1 and Attribute2 are optional input fields to further differentiate an address. For example, if the name of a City and/or State is provided as Address_Part2, it will help differentiate between a common street address [100 Main Street] in different locations.
This match purpose uses the following fields:
  • Address_Part1 (Required)
  • Address_Part2
  • Postal_Area
  • Telephone_Number
  • ID
  • Date
  • Attribute1
  • Attribute2
  • Geocode
To achieve a best of score between Address_Part2 and Postal_Area, pass Postal_Area as a repeat value in the Address_Part2. In that case, the Address_Part2 score used is the higher of the two scored fields.
Organization
Matches organizations primarily by name. It is targeted at online searches when a name-only lookup is required and a human is available to make the choice. Matching in batch requires other attributes in addition to name to make match decisions. Use this match purpose when the rule does not contain address fields. This match purpose allows matches between organizations with an address and those without an address. If the rules contain address fields, use the Division match purpose.
This match purpose uses the following fields:
  • Organization_Name (Required)
  • Address_Part1
  • Address_Part2
  • Postal_Area
  • Telephone_Number
  • ID
  • Date
  • Attribute1
  • Attribute2
  • Geocode
To achieve a best of score between Address_Part2 and Postal_Area, pass Postal_Area as a repeat value in the Address_Part2 field.
Division
Identifies an Organization at an Address. Use this match purpose after a search by Organization_Name or by Address_Part1, or both.
This match purpose is in essence the same match purpose as Organization, except that Address_Part1 is a required field. For example, this match purpose is designed to match company X at an address of Y or company Z at address W if multiple addresses are supplied.
This match purpose uses the following fields:
  • Organization_Name (Required)
  • Address_Part1 (Required)
  • Address_Part2
  • Postal_Area
  • Telephone_Number
  • ID
  • Attribute1
  • Attribute2
  • Geocode
To achieve a best of score between Address_Part2 and Postal_Area, pass Postal_Area as a repeat value in the Address_Part2 field.
Contact
Identifies a contact within an organization at a specific location.
Use the match purpose after a search by Person_Name. However, either Organization_Name or Address_Part1 can be used as the search criteria.
This match purpose uses the following fields:
  • Person_Name (Required)
  • Organization_Name (Required)
  • Address_Part1 (Required)
  • Address_Part2
  • Postal_Area
  • Telephone_Number
  • ID
  • Date
  • Attribute1
  • Attribute2
  • Geocode
To achieve a best of score between Address_Part2 and Postal_Area, pass Postal_Area as a repeat value in the Address_Part2 field.
Corporate_Entity
Identifies an Organization by its legal corporate name, including the legal endings such as INC and LTD. This match purpose is designed for applications that need to honor the differences between such names as ABC TRADING INC and ABC TRADING LTD.
Use this match purpose after a search by Organization_Name.This match purpose is in essence the same match purpose as Organization, except that tighter matching is performed and legal endings are not treated as noise.
This match purpose uses the following fields:
  • Organization_Name (Required)
  • Address_Part1
  • Address_Part2
  • Postal_Area
  • Telephone_Number
  • ID
  • Attribute1
  • Attribute2
  • Geocode
To achieve a best of score between Address_Part2 and Postal_Area, pass Postal_Area as a repeat value in the Address_Part2 field.
Wide_Contact
Loosely Identifies a contact within an organization without regard to location.
Use this match purpose after a search by Person_Name.
In addition to the required fields, ID, Attribute1 and Attribute2 can be provided optionally for matching to further qualify a contact.
This match purpose uses the following fields:
  • Person_Name (Required)
  • Organization_name (Required)
  • ID
  • Attribute1
  • Attribute2
Fields
Provided for general, nonspecific use. This match purpose has no required fields. All field types are available as optional input fields.

0 COMMENTS

We’d like to hear from you!