Why a name-only join loses information

A worked example using a hypothetical scenario to show how the reasoning applies.

The scenario

Two hypothetical supplier records both say "Silver Bridge". One has a different country suffix and birth year. Joining only on the displayed name can merge distinct horses. An unresolved mapping is better than a confident false match. The teaching validator demonstrates record shape, while identity resolution still needs explicit rules.

What to take from it

Stable identifiers support reliable links and historical corrections. They are a foundation rather than a guarantee of data quality.

What to check next

• Separate horse identity from runner identity.
• Store external source IDs with a source namespace.
• Keep an audit trail when two records are merged or split.

Keep the conclusion specific

Separate the observation, the interpretation and the unresolved question. A worksheet is most useful when its conclusion stays within the evidence entered into it.

The example schema is local teaching material, not a supplier specification.