Field Name |
Description / Valid Values |
---|---|
CollectionNumber |
Identifies a collection of duplicate records. The possible values are 1 or greater. |
ExpressMatchIdentified |
Indicates whether the match was obtained using the express match key. The possible values are Yes or No. |
MatchRecordType |
Identifies the type of match record in a collection. The possible values are:
|
MatchInfo |
It displays the detailed information of each match record in JSON format, for example, a match record's name, type, state as True or False, and score of the algorithm between 0-100. Note: This field is displayed only for a duplicate match record.
|
MatchInfo.RuleName.IsMatch |
Displays the match state for the rule. Note: This field is displayed only for a duplicate match record.
|
MatchInfo.RuleName.Score |
Displays the match score for the rule. The possible values are 0-100, with 0 indicating a poor match and 100 indicating a perfect match. Note: This field is displayed only for a duplicate match record.
|
MatchInfo.RuleName. |
Displays the match state for each node in the rule hierarchy, only if it has participated in the matching process, else, a blank field is displayed. Note: This field is displayed only for a duplicate match record.
|
MatchInfo.RuleName. |
Displays the match score for each node in the rule hierarchy, only if it has participated in the matching process, else, a blank field is displayed. Note: This field is displayed only for a duplicate match record.
|
MatchRuleName |
Displays the name of the match rule against which matching is performed. |
MatchScore |
Identifies the overall score between two records. The possible values are 0-100, with 0 indicating a poor match and 100 indicating an exact match. |
Note: The Validate Address and Advanced Matching stages both use the MatchScore field. The MatchScore field value in the output of a dataflow is determined by the last stage to modify the value before it is sent to an output stage. If you have a dataflow that contains Validate Address and Advanced Matching stages and you want to see the MatchScore field output for each stage, use a Transformer stage to copy the MatchScore value to another field. For example, Validate Address produces an output field called MatchScore and then a Transformer stage copies the MatchScore field from Validate Address to a field called AddressMatchScore. When the matcher stage runs it populates the MatchScore field with the value from the matcher and passes through the AddressMatchScore value from Validate Address.