Hello Ed!
I think this use case can be handled using Reltio Workflow. This tool allows managing different business processes right in Reltio UI. One of the things it can do is a Potential Match Review process. You can create instances of this process for your potential matches, assign the review tasks to data
stewards, leave comments for the tasks. By default, this process allows the same 2 actions (Merge or Set as Not-A-Match), but this process is customizable. For example, it's possible to add another step (like Deferred). So the process can look like this:
1. A data
steward reviews a pair and decides that it needs to be deferred
2. He/she executes a "Defer" action. The task state changes from "Review" to "Deferred". It's also possible to leave a comment with additional details
3. Once the pair is ready to be re-evaluated by a data steward, you execute an action "Back to Review" and the task returns to the "Review" state
The potential match doesn't disappear, but it's marked so that a data
steward can understand that this pair is waiting for further updates and doesn't need to be reviewed.
------------------------------
Maxim Karpov
Senior Software Engineer
Reltio
------------------------------
Original Message:
Sent: 07-14-2021 10:27
From: Ed Mosier
Subject: Way to exclude entities from matching if not a match is set to ANY_MATCHING_ATTRIBUTE?
Gino,
I'll see if I can describe the scenario a little better. If the configuration is set up to re-evaluate for matches as they are updated and two records are deemed to be suspect matches. Is there a way to give stewards two options:
1. Mark as 'not a match', which would prevent the two from being matched again.
2. Close the task so that the records are not merged, but if either record is updated the two could potentially be matched again.
Option 1 would used when there is enough information to determine the two entities are distinct.
Option 2 would be used when there is not enough information to make a definitive determination.
Hope this helps.
Ed
------------------------------
Ed Mosier
Slalom
MO
Original Message:
Sent: 07-14-2021 10:10
From: Gino Fortunato
Subject: Way to exclude entities from matching if not a match is set to ANY_MATCHING_ATTRIBUTE?
Hi Ed,
perhaps I am missing something, but isn't this the default behavior? When records are updated, they are re-evaluated to see if they are a match. If a record has been declared not a match by a data steward it remains not a match. The only way that the records are usually marked as 'not a match' is if a data steward has declared that to be the case via the UI.
gino
------------------------------
Gino Fortunato
Senior Solution Engineer
Reltio
Original Message:
Sent: 07-08-2021 18:09
From: Ed Mosier
Subject: Way to exclude entities from matching if not a match is set to ANY_MATCHING_ATTRIBUTE?
If we update the physical configuration so that the not a match is reset for 'ANY_MATCHING_ATTRIBUTE' is there a way to prevent two entities from being matched even if one is updated? Basically we would want the default behavior to be that records would be re-evaluated if matching fields are updated (in case there isn't enough information for a definitive decision) , unless a steward already determined the two records were distinct and don't need to look at the records again. Thank you!
------------------------------
Ed Mosier
Slalom
MO
------------------------------