Category: Metadata Standards

Authority File

Simply put

An authority file is a controlled list that establishes the standard, agreed way to refer to a particular person, place, thing, or concept so that the same entity is described consistently wherever it appears. For example, it fixes the preferred form of a name or heading and links related or alternative forms to it. This consistency helps users find and connect related records reliably.

Formal definition

An authority file is a controlled vocabulary or index composed of authority records that specify the authoritative form of headings, for people, corporate bodies, places, subjects, or other entities, together with preferred terms, non-preferred (variant) terms, and cross-references, and often a persistent identifier. It supports consistent indexing, retrieval, and linking by resolving variant forms to a single authorized heading. In library and bibliographic contexts it may be distributed in standard formats such as MARC; the concept is typically maintained by an issuing agency, and its scope and structure depend on the standards and practices of the maintaining organization.

Why it matters

Authority files address a persistent problem in recordkeeping and information retrieval: the same person, organization, place, or concept can be referred to in many different ways, which fragments related records and undermines reliable discovery. By fixing an authorized form of a name or heading and linking variant or alternative forms to it, an authority file helps ensure that records about a single entity can be found and connected consistently wherever they appear. This consistency supports the integrity and usability of records over time, particularly as terminology drifts, individuals change names, or organizations restructure.

The value of an authority file typically depends on disciplined maintenance by the issuing or maintaining agency. Because scope and structure vary with the standards and practices of that organization, the reliability of cross-references and preferred terms rests on ongoing governance rather than one-time creation. Where a persistent identifier is associated with an authorized heading, it can further reduce ambiguity by anchoring an entity independently of the particular text used to describe it. In bibliographic and archival settings, distributed authority data, such as headings made available in standard formats, allows consistency to extend beyond a single repository.

The purpose of an authority file can also extend to assurance and verification. For example, the authority file of published patent documents is intended to allow interested parties to assess the completeness of a collection. This illustrates that authority files are not only retrieval aids but can also serve as reference points against which coverage and accuracy are checked, depending on the context and the maintaining organization's aims.

Who it's relevant to

Records Managers and Classification Specialists

Those responsible for classification and controlled vocabulary use authority files to enforce consistent naming and headings across records, reducing fragmentation and improving retrieval. The usefulness of an authority file in this setting depends on its scope and on ongoing maintenance aligned with the organization's classification practices.

Cataloguers and Bibliographic Staff

In library and bibliographic settings, cataloguers rely on authority records to link bibliographic records to authorized headings. Services that make headings available in standard formats such as MARC allow these staff to browse, view, and reuse authority data within a local system.

Archivists and Metadata Practitioners

Practitioners describing people, organizations, places, and subjects use authority files to fix preferred forms and connect variant terms, supporting the usability and consistency of descriptions over time. The associated cross-references and identifiers help maintain links between related records as terminology changes.

Users Assessing Collection Completeness

In some contexts an authority file serves as a reference point for verification. For example, the authority file of published patent documents is intended to allow interested parties to assess the completeness of a collection, making such files relevant to those checking coverage and accuracy rather than only searching for individual items.

Inside Authority File

Authorized (preferred) headings

The standardized forms of names, subjects, or terms that have been established as the approved entries for use in indexing, classification, or metadata. These provide the consistent value that recordkeeping systems point to when describing records.

Cross-references from variant forms

Links from non-preferred, alternative, or historical forms of a name or term to the authorized heading. These typically guide users and systems from what they might search for to the form actually used, supporting consistent retrieval.

Scope notes and usage guidance

Explanatory notes that define how and when a particular heading should be applied, clarify its boundaries, and distinguish it from related terms. Such notes help maintain consistent application across those who classify or describe records.

Relationship structure

Recorded connections between headings, which may include broader, narrower, related, or equivalence relationships depending on how the file is structured. This structure supports navigation and helps preserve distinctions between related but separate entities.

Source and maintenance information

Documentation of where an entry was derived from and how it has been reviewed or amended over time. This supports the reliability and traceability of the controlled values, which matters where records must serve as evidence.

Common questions

Answers to the questions practitioners most commonly ask about Authority File.

Is an authority file the same thing as a retention schedule?

No. An authority file is a controlled reference source that governs the standardized form of names, terms, or other access points used in describing and indexing records. A retention schedule, by contrast, governs how long records are kept and what disposition action applies to them. The two serve different functions: the authority file supports consistent naming and classification for retrieval and description, while the retention schedule supports lifecycle and disposition decisions. They may reference one another in practice, but they are distinct instruments and should not be conflated.

Does maintaining an authority file mean my organization has a full classification scheme in place?

Not necessarily. An authority file typically controls the authorized forms and relationships of specific access points, such as personal names, corporate bodies, subjects, or place names. A classification scheme is a broader structure that organizes records into categories reflecting business functions and activities. An authority file can support a classification scheme by standardizing the terms it uses, but on its own it does not constitute a complete classification scheme. The two are complementary rather than equivalent, and their roles depend on organizational policy and the descriptive standards adopted.

How do you decide which access points warrant control through an authority file?

The selection typically depends on which access points are most important for consistent retrieval and description, and where variation in form is most likely to cause confusion. Names of persons, corporate bodies, and jurisdictions, along with recurring subject terms, are often prioritized because inconsistent rendering of these can fragment search results. Organizations generally weigh the retrieval value of controlling a term against the effort of maintaining it. Scope decisions should be documented and aligned with the descriptive standards and business needs of the organization.

What information is typically recorded for each entry in an authority file?

An authority record commonly captures the authorized form of the access point, any variant or non-preferred forms, and cross-references linking related entries. It may also record the sources or rules used to establish the authorized form, notes explaining scope or usage, and administrative details such as who created or revised the entry and when. The specific fields depend on the descriptive standards in use and organizational policy. Recording provenance and revision information can support the integrity and defensibility of the authority file over time.

How should changes to authorized forms be handled once entries are in use?

Changes should generally be managed through a controlled process so that existing descriptions and links remain consistent. When an authorized form is superseded, the former form is often retained as a variant or non-preferred reference rather than deleted, preserving the connection for users who search under the older term. Documenting the reason for the change and the date it took effect supports traceability. The extent to which downstream records are updated depends on system capabilities and organizational policy.

Who is typically responsible for creating and maintaining an authority file?

Responsibility often rests with records management, archival, or descriptive cataloguing staff who apply the relevant standards and rules consistently. In many organizations, a defined role or team oversees the authority file to ensure new entries follow agreed conventions and that changes are governed rather than made ad hoc. Clear ownership helps maintain the reliability of the file, though the exact allocation of responsibility depends on organizational structure and policy. Collaboration with those who create and use the descriptions can improve the file's practical usefulness.

Common misconceptions

An authority file is the same thing as a classification scheme or taxonomy.

While all are forms of controlled vocabulary, an authority file typically focuses on establishing and controlling the authorized forms of specific entries such as names or subjects and linking their variants, whereas a classification scheme organizes records into a hierarchical structure of business functions or activities. They often work together but serve distinct purposes, and the exact relationship depends on how an organization structures its recordkeeping metadata.

An authority file is a permanent, fixed reference that does not need updating.

In practice, authority files usually require ongoing maintenance. Names change, entities merge or dissolve, and terminology evolves, so entries are typically reviewed and amended over time. Treating an authority file as static can lead to inconsistent description and reduced retrieval reliability.

Maintaining an authority file is primarily an archival or library concern with little relevance to active records management.

Controlled, authorized values can support consistent classification, retrieval, and the integrity of metadata throughout the records lifecycle, not only at the point of archival description. Their applicability depends on organizational policy and the systems in use, but the value often extends across active and inactive phases.

Best practices

Establish clear rules for how authorized (preferred) forms are chosen and documented, so that entries are created and applied consistently by different staff over time.

Record cross-references from known variant, historical, and alternative forms to the authorized heading to improve retrieval and reduce duplicate or inconsistent entries.

Assign defined responsibility for maintenance, including periodic review, so that entries are updated as names, entities, and terminology change.

Capture source and change information for entries to support their reliability and traceability, which is particularly important where records must stand as evidence.

Include scope notes or usage guidance for headings that could be confused with related terms, to preserve important distinctions during classification and description.

Align the authority file with related instruments such as classification schemes and metadata standards used in your organization, recognizing that the precise relationship will depend on your systems and policies.