Glossary · 7 · Product information systems and data roles
Golden record
Also known as: Best version of the truth, Master record, Single customer view (customer data)
In master data management, a golden record is the consolidated, agreed version of one business object — a product, material, customer or supplier — built by matching and merging the records that several systems hold about it under defined survivorship rules.
- Data management
- Master data
In one sentence
The consolidated, agreed version of one business object in master data management, built by matching and merging records from several systems.
Example
Three systems hold a pump under slightly different names and weights; matching rules merge them into one golden record with the weight taken from the system defined as authoritative for that attribute.
Explained in context
Context cards connect this term with others to answer one question. Also in British English and German.
- From three readers to check rolesThe home page names three readers — the source, the person and the third reader. Why is that enough to design a check method, and what has to change before a check can run?UKDeutsch
- Who decides which value counts: which system decides a value of product information?When product information passes through PLM, ERP, content systems, spreadsheets, portals and AI functions, how do you tell which system decides a value and which one only holds a copy?UKDeutsch
How it applies
- Survivorship: A golden record is only as good as its rules: which system wins for which attribute, how duplicates are recognized and who resolves conflicts (usually a data steward).
- Product information: For documentation, a golden record is useful for identifiers, names and classifications that many systems share. It tells a writer which identifier and description are agreed across the company.
- Distribution: Once built, the golden record is distributed to other systems by master-data synchronization or read by them on demand.
Golden record vs. released value
A golden record is consistent: the systems agree on it. That does not make it released. A dimension, an interval or a warning text counts for a document only once it has passed the release decision of the system of record that decides it; consolidating unreleased values produces a consistent copy of something nobody approved.
External references
- Gartner, Information Technology Glossary, Master Data Management: https://www.gartner.com/en/information-technology/glossary/master-data-management-mdm