Authorized access point¶

Assign each entity one rule-built, human-readable string that serves at once as heading, retrieval key, and cross-reference anchor — with a disambiguating qualifier carried in the string so two namesakes never collapse into one index entry.

Version: v4 · 2026-09-28 · History · 3 corrections
Domain-specific #: 68
Domain group: Humanities
Origin domain: Linguistics & Semiotics
Subdomain: Bibliographic Authority Control → Linguistics & Semiotics

Core Idea¶

An authorized access point is the sanctioned, standardized string a bibliographic system designates as the canonical retrieval handle for an entity — the exact character sequence, constructed by heading rules, used across every record that mentions it. Built to be unique within the system's universe, it appends a disambiguating qualifier (birth–death years, occupational designation) when two namesakes would otherwise coincide: "Smith, John, 1940–" versus "Smith, John, 1965–".

How would you explain it like I'm…

The Official Name Tag

In a big library, every person gets one exact way their name must be written, and everyone has to write it exactly that way. If two people have the same name, the library adds something extra, like the year each was born, so the two names look different. Then when you look up that exact name, it always takes you to the right person's books.

The Exact Search Name

An authorized access point is the exact, official spelling of a name that a library catalog uses to find things. Every record about that person, place, or thing uses precisely the same string of letters, so searching it always leads to one place. If two people share a name, rules say to add something like birth and death years — for example 'Smith, John, 1940–' versus 'Smith, John, 1965–'. Other spellings and old names are kept as pointers that send you to the official one. It is meant for people to read, unlike a plain ID number.

Standardized Catalog Heading

An authorized access point is the standardized, rule-built text string that a catalog designates as the single official retrieval handle for an entity. Cataloging rules (RDA, and before it AACR2) specify how to build it, including which qualifiers — such as dates or occupation — to add, and in what order, when names would otherwise collide. It does three jobs at once: it is the heading every record uses to refer to that entity, the key the catalog's index is built on, and the anchor that variant names redirect to. It is narrower than an authority record, which is the whole entry containing the heading plus variants, notes, and history. It is also different from an opaque ID number: it is human-readable, because catalogers must be able to construct and check it.

An authorized access point is the sanctioned, standardized string a bibliographic or knowledge-organization system designates as the canonical retrieval handle for an entity: an exact character sequence, constructed by rule and used identically in every record referring to that entity, so that search and browse converge on one place regardless of the starting surface form. It comes from library descriptive practice codified in RDA and its predecessor AACR2 and carried in MARC 21 authority format and BIBFRAME. It is a retrieval-engineering artifact built for uniqueness: when names collide, rules add disambiguating qualifiers (typically dates or occupational terms) in a specified order under specified conditions, governed by an authority file — this governance is what distinguishes it from a mere display label. Operationally it serves three coupled functions: the heading used in name-title, subject, and series fields; the index key for retrieval; and the cross-reference anchor to which variant forms redirect. It is narrower than the authority record that contains it and differs from opaque identifiers such as an LCCN or VIAF cluster ID, sitting between them as a governed, disambiguating, human-readable string. MARC 21 name fields (1XX, 6XX, 7XX) use this form because catalogers must be able to build and verify it.

Scope of Application¶

Lives within bibliographic authority control, where one rule-built human-readable string per entity serves as heading, retrieval key, and cross-reference anchor.

Descriptive heading practice (RDA/AACR2) — rules fix which qualifier to append, in which order, under which authority file.
MARC 21 authority and bibliographic encoding — the 1XX / 7XX / 6XX name, added-entry, and subject fields.
BIBFRAME and linked-data cataloging — the same discipline carried into a linked-data model.
Name-authority resolution workflow — the resolve-before-linking step consulting the governing authority file.

Clarity¶

Naming the access point resolves a three-way confusion between a display label, an opaque identifier, and a governed retrieval string. It fixes the string at the middle position — human-readable like a label but rule-built to be unique like an identifier — and sharpens the question from "what do I call this entity?" to "is this exact string constructed to the rules and distinct from every other?"

Manages Complexity¶

Retrieval consistency is a tangle of obligations: every record must link right, every search converge on one entry, every variant redirect, every namesake collision stay separate. The access point folds all into one engineered string — heading, key, and anchor at once — so the practitioner checks one thing per entity: is this string built to the rules and distinct from every other?

Abstract Reasoning¶

Because the string fuses three functions, it licenses diagnostic inference (an over-merged or scattered index entry points to an omitted qualifier or a rival-heading variant), interventionist prediction (sharpen a qualifier to split a conflated entry; record a variant to redirect it), boundary-drawing (disambiguation lives in the string, not elsewhere; authorized versus variant), and an order-of-construction rule (resolve to the authorized form before linking).

Knowledge Transfer¶

Within authority control the concept transfers as mechanism, diagnostics intact — RDA/MARC/BIBFRAME are co-instances of one retrieval-engineering discipline. Beyond it, what travels is the parent: a governed, disambiguating, unique handle routing all references to one place — recurring as URNs, DOIs, ORCIDs, canonical URLs, and package coordinates. Those disambiguate by opaque construction; the human-readable qualifier-in-the-name convention stays home-bound. The cross-domain weight rides on Signifier–Signified Duality and an Identification-adjacent discipline.

Relationships to Other Abstractions¶

Current abstraction Authorized access point Domain-specific

Parents (2) — outgoing typed relations

Authorized access point is a kind of Preferred label Domain-specific

Authorized access point is a specialization of Preferred label, retaining the parent's defining structure while adding the child's specific commitments.
Authorized access point includes Naming Convention Prime

Naming Convention is an internal constituent of Authorized access point; removing that role breaks part of the child's defining mechanism.

Children (1) — abstractions linked here by typed relations

Authority Record Domain-specific includes Authorized access point

The sanctioned heading string is a strict internal constituent of the full Authority Record, which additionally stores variants, notes, identifiers, and history.

Hierarchy paths (6) — routes to 5 parentless roots

Authorized access point → is a kind of Preferred label → is a decomposition of Arbitrariness of Symbolic Conventions → presupposes Signifier–Signified Duality → is a decomposition of Representation → presupposes Abstraction

Show alternative paths (5)

Neighborhood in Abstraction Space¶

Authorized access point sits in a moderately populated region (50^th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Unclustered & Miscellaneous (2769 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25