Reviewing Deduplication Results and Applying Changes

After you run deduplication, you review the results and accept, reject, or skip the matches for each matched node. Then, you apply the changes to merge the nodes in the viewpoint.

Searching and Filtering Deduplication Results

Searching Deduplication Results

Click the Search icon () and enter text to search for a deduplication result.

Note:

The system searches the current page of deduplication results only. For very large result sets, you may have to page down to load more results in order to search them.

Filtering Deduplication Results

Use the Deduplication Status drop down menu to filter the deduplication results by match status:

• All
• Accepted
• Rejected
• Pending
• Skipped
• Duplicate

Tip:

Click Refresh Results to refresh the filtered match status list.

Accepting, Rejecting, or Skipping Deduplication Results

Select a row in the deduplication results table, and perform an action:

Action	Results
Accept ()	The matched node is deleted and the property and relationship values are merged into the matching candidate node when you apply your changes. The deduplication results table is updated as follows when you accept a match: The Status column for the match candidate that you selected is updated to Accepted. The Status column for all other pending match candidates for this source node is updated to Rejected. The status for skipped items does not get updated. A Merge icon () is displayed next to the node icon for the match candidate. This indicates that the matched node will be merged with this node when you apply the changes. If the matched node is also a match candidate for other matched nodes, those match candidates are marked as Duplicate in the rest of the deduplication results table.
Reject ()	The matched node is kept as a separate node when you apply your changes. The Status column for the match item that you selected is updated to Rejected.
Skip ()	The match candidate is skipped for the current request so that you can re-evaluate it at a later time. The Status column for the match item that you selected is updated to Skipped. Tip: Use Skip to override a previous Accept or Reject action before applying changes. For example, if you initially reject a match candidate and then decide that you want keep that candidate for later evaluation, clicking Skip will undo the reject action. The next time matching is run, that candidate is presented as a potential match.

Selecting the Properties to Keep During a Merge

The Deduplication Details section of the matching workbench displays the properties for both the matched (source) node and the match candidate (target) nodes (see Deduplication Details). By default, the properties and relationships that are merged into a surviving node are defined by the survivorship rule. See Creating, Editing, and Deleting Survivorship Rules.

You can select whether to keep the source or target values for these properties when the nodes are merged by selecting the radio buttons in either the Source Node or the Target Node column for each property. The Keep column indicates whether the value for a property comes from the source or target node.

Note:

You can keep relationship properties for a node only if you are also keeping the node's parent.

Applying Changes from Deduplication Results

After you have accepted at least one deduplication result, click the Apply Changes button to merge the source nodes for all Accepted match results. Applying the changes merges the source nodes for the matches that you accepted with the target nodes in the viewpoint, as follows:

• For the source nodes that were accepted as duplicates, request items are created to delete the source node and remove the node if the deduplicated viewpoint is a hierarchy.
• Properties from the source nodes are merged into the existing target nodes for properties where the Keep column was Source.
• Nodes in hierarchies are either inserted (when shared nodes are enabled) or moved (when shared node are not enabled) to their respective parents that are specified in the source nodes if the Parent property has a Keep column of Source.
• Node links on the surviving nodes are updated as follows:
  • Node links are created on the surviving node for the source nodes that were merged into it.
  • If a duplicate node that is merged already has a node link from another data source, the node link from the original source is updated to point to the surviving node instead.

After you click Apply Changes, the match candidates that have been accepted or rejected are removed from the match results table.

Tip:

To view the candidates in a request that were merged, inspect the request, navigate to the Details tab, and change the request filter to Merged. See Inspecting Requests.

Applying changes from the match process updates the request items in a request, but no changes are committed until the request itself is completed and closed. You can continue to modify the request items (see Inspecting Request Items) before submitting the request.

Discarding Deduplication Results

Click the Discard button on the deduplication results screen to discard all deduplication results that haven't been applied yet. This action removes the deduplication result set from the Deduplication Request Items page and deletes all accepted, rejected, and pending matches for the selected node type and data source. See Deduplication Operations.

Deduplication results that have already been applied are not discarded. You can review and delete those merged request items from the request itself (see Inspecting Request Items).

Rerunning Matches

In the deduplication result set, click Actions and select Rerun to rerun the matching process for this node type and data source. This can be helpful if you have updated your matching rules or you have made changes to the source nodes that were already matched. See Deduplication Operations.