DataTerminology.comNEW
Also known as: Loshin’s Master Data definition
Master data are the core, shared business entities—such as customers and products—used across multiple processes and systems.
DESCRIPTION
David Loshin describes master data as the enterprise’s common, reusable representations of key business entities. These entities support multiple business processes and require strong governance, quality, and integration controls. Effective master data programs harmonize identifiers and attributes to enable a single, consistent view (golden record). Clarity on scope differentiates master from reference and transactional data. Loshin’s framing guides practical MDM implementations.
ALTERNATIVE DEFINITIONS
DATAVERSITY (David Loshin)
Master data represents the common business entities that are shared across multiple application systems, such as customers, products, suppliers, and locations.
Focuses on reuse across systems and core entity examples.
Morgan & Claypool
Master data comprises the key business objects that provide the context for transactional data and are shared across operational and analytical systems.
Highlights contextual role relative to transactions and cross-system sharing.
RELATED TERMS
Master Data Master Data Management Reference Data Single Source of Truth Governance Data Stewardship Data Quality
COMPETING TERMS
RELATIONS
- Broader: Master Data
KNOWLEDGE AREAS
Reference & Master Data Data Management Data Governance Data Architecture
TARGET AUDIENCE
Data Governance Manager Data Steward Data Management Consultant Data Architect Chief Data Officer
EXTERNAL SOURCES
- Wikipedia - Master data management
- DATAVERSITY - Overview by David Loshin
- Gartner - Glossary definition of master data
TOP QUESTIONS
How does David Loshin distinguish master data from transactional data?
Master data defines core entities reused across processes, while transactional data records business events referencing those entities.
Category: Definition
Why is Loshin’s definition useful for MDM programs?
It centers on enterprise reuse and governance, guiding scope selection and prioritization for golden records.
Category: Relevancy
What entities typically fall under master data per Loshin?
Customers, products, suppliers, locations, and similar core business objects are common examples.
Category: Example
How does the definition guide data modeling?
It encourages stable identifiers, harmonized attributes, and clear relationships to transactions and reference lists.
Category: BestPractice
What is a common mistake when applying this definition?
Confusing reference lists or highly volatile operational tables with master entities leads to scope creep and low ROI.
Category: Mistakes
How does governance support master data in this view?
Stewardship, quality controls, and data contracts ensure consistent semantics and distribution across systems.
Category: Management
What metrics show success using this definition?
Reduced duplicate records, higher match accuracy, and consistent reporting across systems signal effective master data management.
Category: Measurement
How does Loshin’s definition compare to Gartner’s?
Both emphasize core entities and consistency; Gartner explicitly mentions identifiers and attributes across the enterprise.
Category: Comparison
Where should teams start with master data using this definition?
Identify high-impact entities, profile data quality, and design matching, survivorship, and distribution processes.
Category: GettingStarted