Configuring a potential match workflow

Configure IBM Match 360 to automatically identify potential match issues and create tasks for data stewards to resolve them by making match or no-match decisions.

When the IBM Match 360 matching engine cannot determine whether two or more records should be matched to form an entity, a data steward review is required. You can configure the potential matches workflow to generate potential match remediation tasks for a data steward.

The IBM Match 360 potential matches workflow type provides the framework for data steward users to:

1. Generate Cloud Pak for Data governance tasks for remediating potential matching issues in your data or a subset of your data.
2. Review and remediate generated tasks by making match or no-match decisions on records for which the matching algorithm cannot make a confident matching decision.

Each record-to-record matching comparison that IBM Match 360 completes generates a matching score. This score can be taken as a percentage value from 0 to 100, with 0 being a definite non-match and 100 being a definite match. As part of configuring the matching algorithm, a data engineer can define two threshold values:

• The autolink threshold defines the minimum matching score for the algorithm to make an automatic match decision between any two records.
• The clerical review threshold defines the minimum matching score for a potential match. Scores below the clerical review threshold are considered non-matches. Scores that fall in the range between the clerical review threshold and the autolink threshold can be sent through the potential matches workflow to be remediated by a data steward user.

If the clerical range is not enabled in the matching settings, then the potential matches workflow cannot generate any tasks. For information about enabling the clerical range and configuring matching thresholds, see Customizing and strengthening your matching algorithm.