Persisting duplicate parties

Some businesses may require you to maintain duplicate parties in InfoSphere® MDM instead of merging or collapsing them. This is known as persistence.

When duplicate parties are persisted, it is expected that the business will maintain multiple profiles of the same party, and these party profiles should not be subject to the InfoSphere MDM party merge functionality.

The default criterion for separating persistent parties is the Line of Business type (LOB) of the duplicate party, meaning that if persistence is configured and duplicate parties have different lines of business, they will be stored as separate records in the system.

These records will not participate in any collapse functionality as the result of any system identified suspected duplicates. However, if a data steward explicitly initiates a collapse using one of the InfoSphere MDM collapse transactions, then these persistent parties can be collapsed.

When your InfoSphere MDM implementation automatically merges parties, the golden record is always available through the related InfoSphere MDM inquiry transactions.

When your InfoSphere MDM implementation does not merge all duplicate parties into a single record, you can still see what it would have looked like if a consolidation had taken place by using the InfoSphere MDM aggregate party view transactions.