Viewing the results of the match and survivorship process in the Staging Data browser
If the records which are pending validation in the Staging Area come from a data model that has a Match Rule attached to it, MDM applies this Match Rule to the records when you launch the validation process, in order to check for matches and decide which values to use for the golden record. This is the match and survivorship process.
During the match and survivorship process, the records pending validation will be matched against the golden record first in an existing match group, and the records that do not match the golden record will be matched against the source record(s) in the match group.
For more information on creating Match Rules and attaching them to a data model, see Match Rules.
The results of the match and survivorship process can be seen in the Staging Data Browser.
The Match group column shows the identifier assigned to each group of matches by MDM.
The Status column shows the results of the process.
|
Status |
Description |
| 000 | New or modified record |
| 202 | Record successfully identified as being part of a group of matching records |
| 203 | Record successfully identified as being part of a group of matching records but the automatic survivorship could not make a trusted golden record because the confidence in the golden record is too low |
| 204 | Record successfully identified as being part of a group of matching records and this record is the unique (golden) record that is submitted to the master database |
| 205 | Record successfully passed the MDM validation phase and also exists in the master database |
| 206 | Record was deleted |
| 403 | Record failed to pass the MDM validation phase, due to a validation issue against the user data model |
| 404 | Record failed to pass the MDM validation phase, due to a constraint issue |
Depending on the criteria defined in the Match Rule, some records may be identified as potential matches that require manual intervention from a data steward to decide if they are true matches or not.
Next time the Staging validation is run, the process looks at how the associated tasks were dealt with and updates the status of the record accordingly. If a task is resolved, for instance, the status of the record changes from 203 to 204 and the record is submitted to the master storage immediately, before ending up with a 205 or 40x status at the end.
If a record is deleted (status 206), it is removed from the match group to which it belongs and the survivorship process is run again.
After you resolve one or more tasks, you have to run the Staging validation again to take into account the record status changes.