Golden record

A golden record is the preferred consolidated representation of an entity in a master-data context. It may combine a stable identifier, selected attributes and links to contributing records. The phrase does not imply that every chosen value is certainly true. A record may contain stale, disputed or missing attributes, and its quality depends on identity decisions and the rules used to select values.

In practice, source records are linked to one entity and their attributes are compared. Some fields may use an authoritative register, others a recent verified source, and some may remain unresolved. The consolidated view should state each field's source and effective date. If underlying evidence changes, the view may change without erasing the earlier state or source assertions.

An organization that must defend a value should be able to move from the golden record back to the competing source records. Otherwise the label golden becomes an unsupported claim of certainty. Master data management governs the wider process; survivorship rules choose among source values; a canonical identifier keeps the identity stable across revisions.

A golden record can mislead in three ways. It can hide disagreement, showing one address when sources hold three. It can mix time, combining a current phone number with a historic legal name as if both described one moment. And it can mix lineage, showing a value as though a single source supplied it when it was assembled from several. Each can be avoided by a design that stores, with each field, the contributing source, the rule applied and the date; Wikidata's treatment of ranks, sources and qualifiers shows one workable model, in which several values for a property coexist, one marked preferred, each with its references.

Monitor the record's quality by sampling. Draw consolidated records at random, trace each field to its sources, and judge whether the rule produced the right value. Report errors by field and by rule, because a rule that works for names may be wrong for addresses. The article on merging or relating organisation records discusses when to avoid a merged record altogether and keep a set of related records with a declared relationship.

Pick any field and ask for its source, rule and date; a record that cannot answer is not defensible. Pick any two source records and ask whether the system treats them as the same entity or different ones, and why. Ask what happens when one source is corrected: whether the consolidated field changes, and whether the change is visible in history. Ask whether a user can see that two values disagreed. And ask how many consolidated records were reviewed by a person in the last period, with what error rate, since an unreviewed golden record has an unknown error rate.