Hello Aishwarya,
I'm not completely sure to understand your question.
But I'll try to provide general information on certification for fuzzy entities.
Fuzzy entities are following below process for certification:
And as you can see, outside of golden authoring via the UI, all integrations must be done via the SD table, which once submitted is kicking the above certification process.
Thank you Alexia,
I get the certification process. But don't understand how whether the match and consolidation would be triggered done there if a change in the source record-
If I have a record that has matched into a group, created a confirmed golden, gets modified in the source database(not semarchy) in such a way that is ceases to match based on any of the match rules. How do I make sure that a match and consolidation step is re-run on this match group, especially when the source record is modified to change an attribute that participates in matching?
I follow the same steps as above to load the record into semarchy, starting with SD table
As long as said record is sent back in the SD table, the certification is kicked, triggering the match and merge process.
Where it will evaluate against all present masters to recompute groups if need be.
Do you have a precise scenario that needs to be analyzed?
Maybe it will be simpler than discussing about generalities.
The precise scenario is this-
A record is already matched and consolidated with other master records to create a golden record(confirmed). The record changes at source such that the match rule should fail and a new singleton golden should be created but. When the updated record is loaded into SD tables and the integration job it run, the changes made to the record do reflect at the master record level, but it does not unmerge and become a separate golden record. I am not sure why it would not unmerge
Got it.
I understand better what is happening.
There is no automatic split in Semarchy.
Hence why it did not occur during the certification.
After you'll split this master from the group via the UI, you should be able to see the appropriate result.
Got it. Thanks Alexia.
I have one more thing to understand.
This would be the case irrespective of whether the golden or the master records are CONFIRMED or NOT_CONFIRMED right?
That is correct, the rule of thumb is no automatic split.
Unrelated to the golden status and so whether there are suggestions or not.
Aishwarya Walia
I am curious to know which scenarios lead to match and merge being done for either full or delta load of new or old records-
Here are a few I can think of:
- Whenever a full load or a delta load where all the records are new i.e. they have never been loaded into semarchy before(and gone through certification process) are loaded
- When a record already loaded and passed through certification has some change since the last load.
I would like to understand if there are any other scenarios as well.Also, I understand that whenever a master record is authored, i.e. if the master record is edited in the UI, it should go through the certification process.
I wanted understand the same for a master record that get modified at the source level, does it have to be updated in SA or SD tables so that it passes through the match and merge step