Reltio Connect

 View Only

  • 1.  Quarantine Potential Matches from OV Exports Until Reviewed by Data Stewards

    Posted 08-20-2025 16:02
    I have a question and wonder if there is a best practice approach to addressing this issue.
    We will soon be adding a few new sources to our organization entity.  Here is the scenario:
    Let's assume that of the 20,000 records with potential matches, 15,000 will be merged to existing OVs after Data Steward review.  The Data Steward review will take some time to get through given the volume.  My concern is that if there are 15,000 records that will eventually be merged to an existing OV, I don't want to clutter consuming systems with "duplicates" that will eventually be merged so as to minimize the noise in the data in those systems and to improve user experience e.g., seeing duplicates, unsure of which record to use.  
    My question from a best practice perspective is how can I "quarantine" these records that are potential matches so that they do not get included in our OV exports until they have been reviewed by a Data Steward and have been determined to be a match or not a match? 


    ------------------------------
    Christopher Brandt
    Clinician Nexus
    ------------------------------


  • 2.  RE: Quarantine Potential Matches from OV Exports Until Reviewed by Data Stewards

    Reltio Employee
    Posted 08-20-2025 16:37

    Hello Chris,

    One option is to add a new attribute to act as a 'Ready to Publish' Flag.

    • Prior to loading the new source data, you can update all existing entities and set the flag to 'true'.
    • The new source data can be loaded with the flag set to 'false'
    • Set the survivorship rule to MaxValue (true > false)
    • Update your export integration to add the flag = true as a filter.

    When you load the new source data, those source records will not be published unless they have been automerged to an existing entity.

    For the new source records that don't have a match, you can run a daily bulk update job to find all entities that have the flag = false but no potential matches and then update the flag to true. 

    The remaining new source record that have a potential match will retain the flag = 'false' value and will not make it to the export.

    Hope this helps.



    ------------------------------
    Bryant Barrenechea
    Solution Architect | Professional Services
    ------------------------------



  • 3.  RE: Quarantine Potential Matches from OV Exports Until Reviewed by Data Stewards

    Posted 08-20-2025 16:46

    Thanks.  That is what we were thinking we would need to do.  Didn't know if there was a more elegant solution.



    ------------------------------
    Christopher Brandt
    Clinician Nexus
    ------------------------------

    Original Message


  • 4.  RE: Quarantine Potential Matches from OV Exports Until Reviewed by Data Stewards

    Reltio Employee
    Posted 08-20-2025 17:03

    Depending on the volume, additional alternatives below:

    1. Clone PROD into a TEST environment and have the stewards work through the matches there. Then you can perform a merge-on-the-fly load into PROD when the matching is complete
    2. Use the Reltio Console external match feature to generate the potential matches report that stewards can review and complete offline. Then perform the merge-on-the-fly load similar to the option above.

    How are you exporting? You may also be be able to adjust the export filter to exclude profiles where there is a potential match (matches > 0) and where the only source in the entity is the new Source Name.



    ------------------------------
    Bryant Barrenechea
    Solution Architect | Professional Services
    ------------------------------

    Original Message


Related Content