Reltio Connect

I attended the 8/19/21 webinar "Rule Based Matching a Deep-Dive" and posted this as agreed during during the session.

The context is initial cut-over and phasing in actual match merges volume to minimize disruption to downstream systems, internal users and actual customers which will result from significant merge of Organizations and Contacts.

Preferred approach would support the following:
1) Initial one-time historically loaded content is not automatically merged (understand this can be accomplished via rules as suggest only)
2) On-going content changes (create or change) are eligible for automatic merge including originally loaded history while at the same time the originally loaded history would not be merged using the automatic rule unless "driven" by newly arriving matched content.
3) In addition to have the capability to drive a controlled volume (based on match rule and other criteria) of specific automatic or suggest rules in an automated fashion.

For purposes of example:

Assume initially loaded "history" data:

a) first name: john   last name: doe       email: john.doe@email.com
b) first name: john   last name: doe       email: john.doe@email.com
c) first name: fred    last name: smith   email: fred.smith@email.com
d) first name: fred   last name: smith   email:fred.smith@email.com
e) first name: jane    last name: doe      email:jane.doe.@email.com]
f)  first name: janet   last name: buck   email:jane.doe@email.com 

Match rule 1:     Automatic after history load;  exact:  first name, last name, email
Match rule 2:     Suggest:   exact email

After history load of a thru f above no automatic merges to be performed

Now on-going process of new content should drive automatic merges:

New content:
g) first name: john   last name: doe       email: john.doe@email.com

      Now we should merge using match rule 1:
              Only records a, b and g since these are "initiated" by new content
              Not records c and d .. even though they meet the rule, don't want to automatically match unless new content drives the match

     While the above processing continues with newly arriving create or change content resulting in automatic merges to existing "history", but no automatic unless new matching content arrives

Hi Mark,

Sorry for the delayed response on this. 

This can be achieved by introducing a new automatic merge rule after the initial data load is complete. Reltio's real-time matching engine is event-based, meaning that matching is triggered only when an existing record is updated or a new record is created.

In addition to this mode, Reltio also supports on-demand matching of the entire tenant's data. If this on-demand match job is run, all existing records will participate in the matching process. Therefore, to avoid matching existing records, these on-demand jobs should not be run.

------------------------------
Suchen Chodankar
Product Manager
Reltio Inc
------------------------------

Original Message:
Sent: 08-19-2021 22:53
From: Mark Burlock
Subject: Match Rule Merge Control: No Pre-Merge of initial Load, Merge New and Updated Content to full Corpus

I attended the 8/19/21 webinar "Rule Based Matching a Deep-Dive" and posted this as agreed during during the session.

The context is initial cut-over and phasing in actual match merges volume to minimize disruption to downstream systems, internal users and actual customers which will result from significant merge of Organizations and Contacts.

Preferred approach would support the following:
1) Initial one-time historically loaded content is not automatically merged (understand this can be accomplished via rules as suggest only)
2) On-going content changes (create or change) are eligible for automatic merge including originally loaded history while at the same time the originally loaded history would not be merged using the automatic rule unless "driven" by newly arriving matched content.
3) In addition to have the capability to drive a controlled volume (based on match rule and other criteria) of specific automatic or suggest rules in an automated fashion.

For purposes of example:

Assume initially loaded "history" data:

a) first name: john   last name: doe       email: john.doe@email.com
b) first name: john   last name: doe       email: john.doe@email.com
c) first name: fred    last name: smith   email: fred.smith@email.com
d) first name: fred   last name: smith   email:fred.smith@email.com
e) first name: jane    last name: doe      email:jane.doe.@email.com]
f)  first name: janet   last name: buck   email:jane.doe@email.com 

Match rule 1:     Automatic after history load;  exact:  first name, last name, email
Match rule 2:     Suggest:   exact email

After history load of a thru f above no automatic merges to be performed

Now on-going process of new content should drive automatic merges:

New content:
g) first name: john   last name: doe       email: john.doe@email.com

      Now we should merge using match rule 1:
              Only records a, b and g since these are "initiated" by new content
              Not records c and d .. even though they meet the rule, don't want to automatically match unless new content drives the match

     While the above processing continues with newly arriving create or change content resulting in automatic merges to existing "history", but no automatic unless new matching content arrives