Evidence architecture and provenance · Lesson 5

Stable identifiers and reversible correction

5 min read

Lesson objectives

  • Design identifiers, version history and correction rules; produce a reversible metadata change record.
Reading tools

It is easy to “fix” a cataloguing error by replacing a field value, but a silent replacement can break links to photographs, research and public labels. A stable identifier does not mean a description is fixed. It is a handle for the same entity while knowledge about it changes. Give a physical vessel an identifier, its photograph another, and an origin claim a third when that decision needs separate review. If two records prove to be about one thing, do not delete an identifier and hope old links will work; record the merge or error and the former identifier's destination. A colleague following an old link should be able to see what changed and why.

Suppose tool A-105 has photograph P-301. A 2015 description linked P-301 to A-105 and generated the public title “Fishing tool.” On examining the mark in the photograph in 2026, staff find it reads A-150, a different object in storage. The correction is more than changing 105 to 150 in a database. Preserve the earlier description and publication date. Add a correction event with the high-resolution image as source, reviewer, old and new link, and confidence status. Inspect every dependent output: webpage title, pictured file, gallery caption and exported research dataset. Do not automatically copy the “fishing” function to A-150; it was an inference from the erroneous link. Review that claim separately. A provisional title may be “tool of undetermined function.”

A good identifier need not encode the object's meaning. It can include a prefix, sequence and duplicate check, but should not imply a manufacture date or material type that could later change. Define allocation rules that prevent reuse even when a record is retired, and cover composite objects and digital copies. If inherited numbers conflict, retain them as former identifiers with their sources, and assign a stable institutional handle to the current entity. Distinguish “this old label was used for the object” from “this object is certainly the one referred to by the old number.” The latter requires matching evidence.

A change record needs fields that permit responsible reversal: change identifier, decision time, evidence reviewer, old and new values, source prompting review, effect on claims and public text, notification method for downstream users, and reopening condition. “Reversal” does not mean erasing a correction later found wrong. Add a new change restoring the value with its reason while retaining the sequence. If earlier versions vanish, staff cannot tell what a published researcher saw before correction, and contradictions become inexplicable. Rights or community requests may restrict public display of some versions. Internal retention of the change trail is a separate records decision from public release.

Before changing a field, run a dependency check: “what points to this identifier?” and “what uses this claim?” In A-105's case, P-301, webpage title, exhibition list and fishing-function note all need inspection. Correct the image link first, then identify texts whose evidence has gone. An A-105 description could still have independent support, so do not indiscriminately delete it. If an external publication used the old wording, provide a traceable correction notice instead of altering a file the institution does not control. This method prevents one “fix” from creating several new errors elsewhere.

Three kinds of change need different treatment. A *transcription correction* occurs when a staff member entered A-105 although the original source clearly says A-150; keep the erroneous value as record history, not as a plausible historical identity. A *reinterpretation* occurs when the card itself says “fishing tool” but new evidence supports another use; the wording on the card remains a fact about the card while the function judgement changes. An *access restriction* occurs when information remains in an internal record but public display is suspended pending a request review; the object's identity does not change. Each affects search results and editorial responsibility differently. Have a second reviewer read the evidence that prompted the change and follow one old link and one new link. If either fails, the correction is not complete even though the main field is now right.

Publish the change in two controlled steps: establish a reference link from the correct photograph identifier to each version, then update dependent public outputs. This avoids a page temporarily showing corrected text beside the wrong image. Schedule another review if the function interpretation is still open. “Correction complete” must not cover an unexamined claim. A practical closure test is whether another curator can identify the intended entity, correction source, earlier version and remaining uncertainty from the record alone.

Lesson summary

It is easy to “fix” a cataloguing error by replacing a field value, but a silent replacement can break links to photographs, research and public labels