Collection item matching examples

This topic includes examples of how items from incoming entities are matched with items in golden records by occurrence and by key.

Omitted and duplicated key fields

When collection key fields are omitted:

• For key-based matching, the entity becomes quarantined.
• For occurrence-based matching, the entity continues incorporation.

When collection key fields are duplicated:

• For key-based matching, the key field values are quarantined.
• For occurrence-based matching, there is no concept of duplication. For occurrence, any field value can be repeated as many times as possible.

Matching by order of occurrence

When the Order of Occurrence option is selected for a collection’s Identify By setting in a domain model, matching of collection items is performed sequentially.

• Nicknames collection represented in the model by the repeatable field Nickname:

• Phones collection represented in the model by the repeatable field group Phone:

Matching by key field values

When the Key option is selected for a collection’s Identify By setting in a domain model, collection items are matched by their key field values.

note

While matching by key field values works the same regardless of whether an entity specifies operations on individual collection items, the following examples show the results in the golden record of incorporating items not specifying item operations. For help in determining results for items specifying operations, see the Related concept about collection item operations.

• Nicknames collection represented in the model by the repeatable field Nickname:

• Phones collection represented in the model by the repeatable field group Phone.

  These sets of examples have the same existing golden record and incoming entity pairings. Observe how the designation of different key fields changes the outcome of matching.

  • The designated key fields are Type and Number:

• The designated key field is Type:

• The designated key field is Number: