IBM InfoSphere MDM Tutorial: Understand Entity Matching and Master Views

Master data management distinguishes source records from the business entities they may describe. An IBM InfoSphere MDM tutorial develops that distinction through matching, linking and survivorship concepts. A consolidated view depends on chosen rules and deployment architecture, so the most recent field value or a high match score should not automatically be treated as unquestionable truth.

Here's a popular IBM InfoSphere MDM video — watch it, then summarize it with one click. Or paste any other YouTube link below.

— or paste your own YouTube link —

Want to keep the key points from a YouTube video? Paste the link below to turn it into structured notes.

Why Use IBM InfoSphere MDM Tutorial: Understand Entity Matching and Master Views

Frequently Asked Questions

Can two source records describe the same entity?

Yes. Different applications can store overlapping or inconsistent information about one person or organization. Resolving that relationship requires identity reasoning across relevant attributes rather than assuming that every database row represents a distinct real-world entity.

Does a matching score prove two records are identical?

A score summarizes evidence under a configured matching approach. Thresholds, attribute quality and the cost of false matches matter, so ambiguous cases can need review instead of being accepted solely because a numerical cutoff was reached.

What is survivorship in an MDM context?

It defines criteria for choosing or composing values in a master view when source information overlaps. Those criteria depend on the business and architecture, rather than universally selecting the newest value for every attribute.

Is a master view always a replacement for every source system?

No. MDM architectures can preserve source records while creating resolved relationships or consolidated representations. Understanding where information is stored and governed is necessary before assuming a correction automatically overwrites every contributing application.

Why retain the provenance of a selected attribute?

Provenance explains which source and rule contributed the value, supporting investigation when sources disagree. A master view becomes easier to govern when its contents are explainable rather than presented as an untraceable final answer.