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

Match Process

Match Process

Before records in a base object can be consolidated,
Informatica MDM Hub
must determine which records are likely duplicates, that is matches, of each other.
The match process uses match rules to perform the following tasks:
  • Identify which records in the base object are likely duplicates (identical or similar)
  • Determine which records are sufficiently similar to be consolidated automatically, and which records should be reviewed manually by a data steward prior to consolidation
In
Informatica MDM Hub
, the match process provides you with two main ways in which to compare records and determine duplicates:
  • Fuzzy matching is the most common means used in
    Informatica MDM Hub
    to match records in base objects. Fuzzy matching looks for sufficient points of similarity between records and makes probabilistic match determinations that consider likely variations in data patterns, such as misspellings, transpositions, the combining or splitting of words, omissions, truncation, phonetic variations, and so on.
  • Exact matching is less commonly-used because it matches records with identical values in the match column(s). An exact strategy is faster, but an exact match might miss some matches if the data is imperfect.
The best option to choose depends on the characteristics of the data, your knowledge of the data, and your particular match and consolidation requirements.
During the match process,
Informatica MDM Hub
compares records in the base object for points of similarity. If the match process finds sufficient points of similarity (identical or similar matches) between two records, indicating that the two records probably are duplicates of each other, then the match process:
  • populates a match table with ROWID_OBJECT references to matched record pairs, along with the match rule that identified the match, and whether the matched records qualify for automatic consolidation.
    An example showing the data flow during the match process.
  • flags those records for consolidation by changing their consolidation indicator to 2 (ready for consolidation).
If you configure data encryption, the
MDM Hub
cannot generate match keys if encrypted columns are included in the match rules, and therefore cannot perform match jobs.

0 COMMENTS

We’d like to hear from you!