OneData 10.7 | Managing Master Data with webMethods OneData | webMethods OneData Consolidation MDM Guide | Use Case To Understand The Basic Configuration | Configurations for the Matcher | Matching Configurations
 
Matching Configurations
In the Matching Configuration screen, you specify how OneData should use the score returned by each rule to create a Gold record or link the matched record, or keep the matched record unchanged, so that the Data Steward can take the necessary actions.
The match ranges could be any of the following:
*Good match range. When matching server returns a score that falls between the good match range and 100, the Gold record is considered a match to the record from the consolidation table.
*Suspect match range. When matching server returns a score that falls between the suspect match range and good match range, the Gold record is a suspect match to the record from the consolidation table.
*Below Suspect range. When matching server returns a score that falls below the suspect match range, the Gold record is not considered a match to the record from the consolidation table.
You can set the following matching actions for Good, Suspect, and Below Suspect matches:
Matching Action
Description
Process best match
If there is more than one match in the consolidation Gold object, this option links the Consolidation record to the match in the consolidation Gold object with the highest score.
Process only if single match
This option links the Consolidation record to the Gold record only if there is one match in the good match range in the Consolidation Gold object. If there are multiple matches, the matching server does not process the Consolidation record. Manual matching is required.
Queue for manual matching
This option keeps the consolidation (staging) as cleansed, so that it can be handled later through a manual match. You can select the user group to notify in Notification. The records appear in the My Data Quality Inbox of every user in the Data Quality Steward Group.
Do not process
Available only for Below Suspect Match, this option is only applicable to records that do not achieve suspect match, at minimum. The matching server does not perform any action on the Consolidation record.