I have my model configured such that the match group scoring is set to use transitive scoring. The model goes through a deployment cycle i.e. DEV, QA, PROD deployment has taken place and records have been loaded and passed through the certification process. It is now decided that we want to move to multi-iteration grouping with direct scoring only and the transitive scoring checkbox is unchecked. Now, how do I make sure that each of the existing match groups go through the certification process so that they records now use direct scoring?
Best Answer
A
Alexia SIMOND
said
11 months ago
Hello Aishwarya,
A change in the matching properties is still a change of matching.
Thus you'll need to replay matching to process those changes.
I'm leaving here the documentation section on how to do so:
Hi Alexia, Is it absolutely necessary to reset user decisions each time matching is replayed? Does the action of resetting user decision mean that whatever merge or split action would have been done by the UI users would now be reset? Or does it reset all the matches irrespective of how they were done i.e. by the users or semarchy?
A
Alexia SIMOND
said
11 months ago
Resetting user decisions is indeed necessary if you want the matching to replay on all records (and not only the ones issued from the certification match and merge process).
Otherwise, all the records issues from manual actions will remain as such and not be replayed as part of this replay matching process.
Aishwarya WALIA
I have my model configured such that the match group scoring is set to use transitive scoring. The model goes through a deployment cycle i.e. DEV, QA, PROD deployment has taken place and records have been loaded and passed through the certification process.
It is now decided that we want to move to multi-iteration grouping with direct scoring only and the transitive scoring checkbox is unchecked.
Now, how do I make sure that each of the existing match groups go through the certification process so that they records now use direct scoring?
Hello Aishwarya,
A change in the matching properties is still a change of matching.
Thus you'll need to replay matching to process those changes.
I'm leaving here the documentation section on how to do so:
https://www.semarchy.com/doc/semarchy-xdm/xdm/latest/Integrate/manage-duplicates-with-sql.html#_replay_matching
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstAlexia SIMOND
Hello Aishwarya,
A change in the matching properties is still a change of matching.
Thus you'll need to replay matching to process those changes.
I'm leaving here the documentation section on how to do so:
https://www.semarchy.com/doc/semarchy-xdm/xdm/latest/Integrate/manage-duplicates-with-sql.html#_replay_matching
Aishwarya WALIA
Hi Alexia,
Is it absolutely necessary to reset user decisions each time matching is replayed?
Does the action of resetting user decision mean that whatever merge or split action would have been done by the UI users would now be reset? Or does it reset all the matches irrespective of how they were done i.e. by the users or semarchy?
Alexia SIMOND
Resetting user decisions is indeed necessary if you want the matching to replay on all records (and not only the ones issued from the certification match and merge process).
Otherwise, all the records issues from manual actions will remain as such and not be replayed as part of this replay matching process.
-
LOV label in Named Query
-
How we can set Dynamically changing Form field Description?
-
Is it possible to have a conditional survivorship rule based on a SemQL filter (akin to the filter on privileges)?
-
Where Do I View 2 Merged Records?
-
Show/hide an attribute in a form
-
Restrict access of attributes
-
Is it possible to manage visible/invisible value in List depend on user role??
-
Why am I unable to merge duplicates?
-
How are child records selected when parent records are manually merged?
-
Can the response from the API Call Response can be formatted differently in the JSON output?
See all 178 topics