Output - 23.1

Spectrum Dataflow Designer Guide

Version

23.1

Language

English

Product name

Spectrum Technology Platform

Title

Spectrum Dataflow Designer Guide

2024

First publish date

2007

Last updated

2024-10-11

Published on

2024-10-11T22:55:47.128293

Table 1. Transactional Match Output
Field Name	Description / Valid Values
HasDuplicates	Identifies whether the record is a duplicate of another record. One of the following: Y The record is a suspect record and has duplicates. N The record is a suspect record and has no duplicates. D The record is a candidate record and is a duplicate of the suspect record. U The record is a candidate record but is not a duplicate of the suspect record.
DuplicateCount	It displays the number of duplicates within a match group.
MatchGroupSize	It determines the size and displays the number of records in a match group.
MatchRecordType	Identifies the type of match record in a collection. The possible values are: Suspect The original input record that was flagged as possibly having duplicate records. Duplicate A record that is a duplicate of the input record. Unique A record that has no duplicates.
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 between 0-100.
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.
MatchInfo.`RuleName`.IsMatch	Displays the match state for the rule as `True` or `False`, with `True` representing a match and `False` indicating no matches. This information is displayed if you select the Return detailed match information option in the Transactional Match Options screen. Note: The value in this field is derived from the match state of the child nodes based on the defined parent rule configuration.
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. This information is displayed if you select the Return detailed match information option in the Transactional Match Options screen. Note: The score in this field is derived from the scores of the child nodes on the basis of the defined parent rule configuration.
MatchInfo.`RuleName`.`RuleNodeName`.IsMatch	Displays the match state for each node in the rule hierarchy as `True` or `False`, with `True` representing a match and `False` indicating no matches. `RuleNodeName` is a variable, which is replaced by the hierarchical node names in your match rules. Each node in the rule hierarchy outputs this field, if you have selected the Return detailed match information option in the Transactional Match Options screen.
MatchInfo.`RuleName`.`RuleNodeName`.Score	Displays the match score for each node in the rule hierarchy. `RuleNodeName` is a variable, which is replaced by the hierarchical node names in your match rules. Each node in the rule hierarchy outputs this field, if you have selected the Return detailed match information option in the Transactional Match Options screen. The possible values are 0-100, with 0 indicating a poor match and 100 indicating a perfect 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.