IS_DUPLICATE_OF Party-to-Party
Description
Use the IS_DUPLICATE_OF relationship to record a stewardship decision around de-duplicating parties. This is intended to provide signals to downstream systems around duplicates they will need to resolve in their systems.
Recording the duplicate relationship is the last step in a stewarding process described in Duplicate Parties.
Label
:IS_DUPLICATE_OF
Valid nodes
| From | Relationship | To | Cardinality |
|---|---|---|---|
| Duplicate Party A node with the :Party label | :IS_DUPLICATE_OF | Party A node with the :Party label | 0..1 |
Properties
IS_DUPLICATE_OF uses the standard relationship properties.
CREATE
An invalid party can be a duplicate of zero or one valid parties.
The IS_DUPLICATE_OF relationship connects a primary party with its duplicate entries in the graph. There may be cases where we first have two sets of duplicates marked independently:
(a:Party)-[rAB:IS_DUPLICATE_OF]->(b:Party)(c:Party)-[rCD:IS_DUPLICATE_OF]->(d:Party)
We later discover and mark (b:Party)-[rBD:IS_DUPLICATE_OF]->(d:Party). In this case, we must first deactivate the IS_DUPLICATE_OF relationships between A & B and C & D and create the following new relationships to avoid creating a tree of duplicates:
(a:Party)-[rAD:IS_DUPLICATE_OF]->(d:Party)(b:Party)-[rBD:IS_DUPLICATE_OF]->(d:Party)(c:Party)-[rCD:IS_DUPLICATE_OF]->(d:Party)
Creation of IS_DUPLICATE_OF relationships is limited only to DMO personnel.
IS_DUPLICATE_OF relationships are valid between any two nodes with the :Party label.
UPDATE
Updates to the IS_DUPLICATE_OF relationship are not allowed. To update an relationship, deactivate the ecisting relationship and create a new IS_DUPLICATE_OF relationship.
DELETE
Deleting an IS_DUPLICATE_OF relationship is a deactivation. No physical deletes will happen.