Relationships

Data stewards and data managers can view, manage, and create relationships between different data types.

Relationships are tightly integrated with data resolution so data stewards can be certain that the relationships they are managing are based on a single trusted view of the data. This integration further benefits data stewards through visual alerts that records involved in relationships may have data quality issues – data stewards can navigate between relationship and data resolution to ensure they are making business decisions with the best data possible.

There are two primary categories of relationships that must be managed:

• Reflexive, peer-to-peer – an example of this relationship type would be 3 different entities that are in a group. Another example is a traditional Identity with representation from two or more entities.
• Non-reflexive – this includes two basic subtypes:
  • Parent-child – such as in a hierarchy.
  • Order relevance – such as an individual at an organization.

Entity to entity relationship types

• Family relation – all relevant records may be from the same or different sources and of the same record type, but may have relationships that are with positional relevance.

  EX: There are 4 records: Adult male, Adult female, Boy, and Girl. There are 6 different relationships between them.

• Non-peer association – this is a classic many-to-many entity relationship because an individual may have zero-to-many relationships with Organizations, and an Organization may have zero-to-many relationships with individuals.
• Peer-to-peer relationships – these are groupings of entities with no positional context in their relationship. It is an effective way to establish a group or collection of entities.

Within InfoSphere® MDM Inspector, users will be able to view relationships, and review and resolve tasks.