Fields Automatically Adjusted During Duplicate Resolution

When you modify records in the duplicate resolution view of the Data Stewardship Portal, some fields are automatically adjusted to reflect the record's new disposition.

Table 1. Records Processed by Interflow or Intraflow Match
Action Values Automatically Applied to Fields

Moving a record from one collection to another
If you move a record into a collection of duplicates:
  • MatchRecordType: Duplicate
  • MatchScore: 100
  • HasDuplicates: D (This field is only present if the dataflow contained an Interflow Match stage.)
If you move a duplicate record into the collection of unique records (collection 0):
  • MatchRecordType: Unique
  • MatchScore: No change
  • HasDuplicates: U (This field is only present if the dataflow contained an Interflow Match stage.)
If you move a suspect record into the collection of unique records (collection 0):
  • MatchRecordType: Unique
  • MatchScore: 0
  • HasDuplicates: N (This field is only present if the dataflow contained an Interflow Match stage.)

Creating a new collection
  • MatchRecordType: Suspect
  • MatchScore: No value
  • HasDuplicates: Y (This field is only present if the dataflow contained an Interflow Match stage.)
Note: If the record came from a dataflow that contained an Interflow Match stage only records with a value of "input_port_0" in the InterflowSourceType field can be a suspect record.
Table 2. Records Processed by Transactional Match
Action Values Automatically Applied to Fields

Change MatchRecordType to Duplicate
  • HasDuplicates: D
  • MatchScore: 100

Change MatchRecordType to Unique
  • HasDuplicates: U
  • MatchScore: unchanged

Change HasDuplicates to D
  • MatchRecordType: Duplicate
  • MatchScore: 100

Change HasDuplicates to U
  • MatchRecordType: Unique
  • MatchScore: unchanged

Change HasDuplicates to Y
  • MatchRecordType: Suspect
  • MatchScore: blank

Change HasDuplicates to N
  • MatchRecordType: Suspect
  • MatchScore: blank