OneData 10.7 | Managing Master Data with webMethods OneData | webMethods OneData Consolidation MDM Guide | Working with Data Quality Projects | Working with Matching Projects for Consolidation Objects | Defining Rules and Rule Mappings for a OneData Matching Project | Default Outbound Attributes for Matcher Projects
 
Default Outbound Attributes for Matcher Projects
This section describes the details of each outbound attribute usage.
Attribute
Attribute Type
Description
Hint
Outbound
A description on how the score and pattern were obtained. 400 characters is the preferred width of the staging column to which this attribute is mapped. To accommodate the possibility of a longer string, make suitable changes to the width of the staging column in the object definition so that the column holds the full string length.
Pattern
Outbound
Using the customer domain example, the possible values are:
*MASTER. Relevant only in a Multiple-Table Gold model. It indicates that only the customer attributes have matched. So there is a new address for the existing customer.
*BOTH. Relevant only in both Multiple-Table Gold and Single-Table models. In a Multiple-Table Gold model, it indicates that both the customer and address attributes have matched. In a Single-Table model, BOTH is the only value possible as all customer information is available in a single table.
18 characters is the preferred width of the staging column to which this attribute is mapped.
Score
Outbound
Values could be any number between 0 and 100. It indicates the similarity between the Consolidation and Gold records. 10 characters is the preferred width of the staging column to which this attribute is mapped.
Match Type
Outbound
Type of match executed:
*Good Match. When the score is greater than or equal to the good match threshold.
*Suspect Match. When the score is less than the good match range, but greater than or equal to the Suspect Match threshold.
*Below Suspect Match. When the score is less than the suspect match range.
*No Match. When no match candidates are available.
*Manual Match. On manual execution of the match hook.
50 characters is the preferred width of the staging column to which this attribute is mapped.
Matcher Action
Outbound
Includes the action set by the user in the Matching Configuration for each Match Type and details of how the action was executed. 200 characters is the preferred width of the staging column to which this attribute is mapped.
Possible values are:
*Create Gold - Created
*Process best match – Linked to existing gold record
*Process only if single match – Queued for manual match
*Process only if single match – Linked to existing gold record
*Queue for manual matching - Queued
*Do not process - No action
*Manually linked to existing gold record
Details
Outbound
Describes the reason for the matcher action. 200 characters is the preferred width of the staging column to which this attribute is mapped.
Possible values are:
*Gold record created
*Single match candidate found
*Multiple match candidates found
*All match candidates below Suspect Match
*No match candidate found
*Left for manual match
*Manual matching executed
*Queued for manual match
For example, let us assume you configured Action as Process only if single match for Good Match. Subsequently, the matcher executed the action Queued for manual match. The Details attribute explains that the reason for the matcher action. The reason might be, for example, Multiple match candidates found.
Project
Outbound
Name of the data quality project used to run the matching process. 400 characters is the preferred width of the staging column to which this attribute is mapped. To accommodate the possibility of a longer string, make suitable changes to the width of the staging column in the object definition so that the column holds the full string length.