A curated list of authorized headings (forms of names, corporate bodies, subjects, etc.) and stable identifiers, together with variant forms and relevant relationships, maintained to ensure consistent naming, disambiguation, and linking across bibliographic records and discovery systems.

Principle

By assigning an authorized heading and a persistent identifier to each distinct entity and recording variants and relationships, an authority file enforces consistent representation and enables disambiguation and reliable linking across records and systems.

Demonstration

Situation: A cataloger encounters two records for works attributed to “J. M. Lee.” Recognition: The authority file contains distinct authority records (authorized heading + identifier) for two different persons with variant forms. Action: The cataloger links each bibliographic record to the correct authority identifier. Consequence: Searches and aggregates that use the authority identifier return works for the intended individual without conflating different people.

Misapplication

Assuming an authority file is exhaustive or universally canonical and therefore merging records from different local authorities without reconciliation. The semantic error is treating identity‑strings (labels) as sufficient proof of identity rather than requiring an authoritative identifier and context; this can conflate distinct entities.

Consequence

Proper use improves discovery accuracy, supports record deduplication and reliable aggregation, and enables cross‑collection linking. Misuse—e.g., uncontrolled merging or ignoring provenance—causes conflation of distinct entities, loss of attribution, and misleading search results.

Reversal

In distributed linked‑data environments, multiple authority files may coexist for the same entities; reconciliation requires explicit mappings, provenance, or use of globally unique identifiers. In some user‑facing contexts, displaying commonly used name forms may be prioritized over the authorized form.

Boundary

Clearly within: a maintained authority list that provides an authorized heading, variant forms, an identifier, and documented scope and relationships. Boundary case: a local name list recording preferred labels without stable identifiers or provenance. Clearly outside: uncontrolled free‑text name entries or user tags without curated variants or identifiers.

Semantic Tension

Uniqueness/disambiguation (stable identifiers and authoritative forms) ↔ Cultural/linguistic variation (multiple legitimate name forms and local naming conventions) that complicate canonicalization.

Synthesis

An authority file is infrastructural: it maps lexical variants to authoritative headings and persistent identifiers so that names function as stable referents across cataloging, discovery and linking rather than as ambiguous text strings.