Suspect match
The degree to which a record comparison is considered a potential or true match. level; however, data steward intervention is required for records that are similar but not necessarily the same. These matches are called suspect matches, since the confidence level is not high enough to act on the match automatically. Suspect matching helps to preserve data quality by finding records that are potential duplicates.
Suspect matches are initiated through the following workflows:
- Source subscriptions - Depending on the match rules A definition that determines which fields in a record are a possible match and when a record comparison is considered a suspect match. See features and feature sets., records from source subscriptions An external source of data, such as Concur or SAP. A source subscription defines the data model, job scheduling, and other configuration for the data import. can be forwarded to the data steward inbox as suspect matches.
- Add requests - When the match confidence level is not high enough, a suspect match task is forwarded to the data steward inbox.
- Profiles - From the profile page of valid customer records, data stewards can use Find Suspect Match to search for potential duplicates.
- Network API - Using an API call, suspect match tasks can be created through customer web portals.
Enabling this feature
Suspect match is enabled by default.
Match rules must be defined in source subscriptions so that suspect matches can be found.
User activities
The following activities are available depending on the user type:
| Activity | Standard User | Data Steward | Data Manager | Administrator |
|---|---|---|---|---|
| Define match rules |
|
|
||
| Run source subscription |
|
|
||
| Analyze match logs | ||||
| Search for suspect matches |
|
|
||
| View and assign suspect matches in the inbox |
|
|
||
| Accept or reject suspect matches |
|
|||
| Report on suspect matches |