Suspected duplicate task resolution

A suspected duplicate task is assigned when two or more records from the same source appear to be the same member. There are specific steps that you can take to resolve tasks of this type.

In this example, different Source IDs are assigned. However, the names and personal identification numbers are similar, while other attribute values are identical.

Table 1. Suspected duplicate task records
Record 1 Record 2
Source A
Source ID: 895677		 Source A
Source ID: 895688
Name: John Q. Public Name: John Public
Personal ID number: 482-89-1822 Personal ID number: 422-89-1822
Phone: 480-555-6060 Phone: 480-555-6060
Date of birth: 10/14/70 Date of birth: 10/14/70
Gender: M Gender: M
Occupation: Engineer Occupation: Engineer
Address: 1043 W. Easy St

Phoenix, AZ 85545

 Address: 1043 W. Easy St

Phoenix, AZ 85545
Employer: ReallyBigCorp Employer: ReallyBigCorp

After you review the records and determine that they are the same member, follow these steps.

  1. Identify which record of the two you want to be the surviving record and which one you want to become obsolete.
  2. Change the EID for the obsolete member to the surviving member (drag the obsolete member onto the surviving member in the Inspector application).
  3. Edit the task status for each record to indicate that the task was reviewed and the records are the same member.
  4. Make any edits to attribute values and status as necessary.

    Again, if your implementation supports updates to the source, a message is sent through the outbound broker.

    Note: When you edit the attributes during resolution of a suspected duplicate task, make sure that you edit attributes for the surviving record.

    If you determine that the records are not the same, follow these steps.

    1. Verify that both records do not share common Source ID and Entity ID numbers.
    2. Edit the task status for each record to indicate that the task was reviewed and that the records do not represent the same member.