Unmarking a Record as a Duplicate

A record that has been marked as a duplicate can be unmarked. For example, if the organization discovers that two records do not relate to the same person, it can unmark the record that was marked as a duplicate. Unmarking a duplicate effectively breaks the link between the two records.

When a record is unmarked, the reason for unmarking the record as a duplicate is recorded, e.g., input error, not a duplicate. The name of the user who unmarked the record and the date the record is unmarked is automatically recorded by the system.

If a record is unmarked as a duplicate, the system automatically notifies the case owner of any cases on which the duplicate participant is the primary client in the event that further action has to be taken on the case. For example, Jim was merged to James Smith. The user had selected to merge Contact Details on Jim's record to James' record. When it was realized that these two individuals were merged in error, they were unmarked.

The contact details that were merged to James Smith's record must be manually removed. Unmarking breaks the links between the 2 individuals, but any details selected during the merge process will need to be manually removed by the caseworker.

Note: If identification information is merged from a duplicate record to a master record and it is later discovered the records do not relate to the same person, the identification record must be manually canceled from one of the records before the duplicate record can be unmarked. This is because only one identification reference is allowed to exist in the system for certain types across all person participants.