Skip to content

Entry Term Alias

Curate a non-preferred surface form — synonym, abbreviation, colloquialism, superseded name — as a silent, non-indexing bridge that routes many-to-one to a canonical descriptor, so users arrive at one place however they name the concept.

Core Idea

An entry term alias is a non-preferred surface form — a synonym, abbreviation, alternate spelling, colloquial phrase, or superseded name — that is curated in a controlled vocabulary not as an independent descriptor but as a silent routing bridge to the canonical descriptor it represents, so that users who know the concept by any of its common names arrive at the same place.

In MeSH the structure is explicit: each descriptor may carry many entry terms, also called "see from" references or synonyms in the record. The entry term "heart attack" routes to the descriptor "Myocardial Infarction"; "vitamin C" routes to "Ascorbic Acid"; "AZT" routes to "Zidovudine." The entry terms have no independent indexing status — no article is indexed under "heart attack" as a heading — but the PubMed search interface, when given "heart attack" as a query term, automatically expands it to "Myocardial Infarction" and retrieves the controlled descriptor's indexed records. The user never sees the routing; the system performs it silently. In LCSH the equivalent mechanism is the UF ("Used For") field on an authority record: "UF Automobiles" under the heading "Motor vehicles" means that a search for "Automobiles" silently delivers "Motor vehicles" results.

The relational structure is a many-to-one asymmetric mapping with a routing contract. Many entry terms map to one canonical descriptor; the reverse relation does not hold — the canonical descriptor does not "route to" any of its entry terms, it merely lists them as metadata. The canonical descriptor is the form that gets indexed and displayed; the entry terms are the form the vocabulary absorbs without promoting. This asymmetry is what distinguishes entry-term aliasing from synonymy as a symmetric equivalence relation: the alias and the canonical form are not interchangeable equals; the alias is subordinate, non-indexing, and directionally committed.

The vocabulary maintainer's discipline consists of curating the alias inventory as the literature and user behavior evolve: adding new entry terms when a new colloquial phrase gains traction, retiring entry terms when a form becomes so rare it generates more confusion than recall, and noting deprecated forms of a canonical descriptor that has itself been renamed (in which case the old preferred form may become an entry term pointing to the new one). This curation work is the mechanism by which the vocabulary absorbs natural-language variation at the input surface while keeping the descriptor set stable at the indexing and retrieval surface — the operational division that makes a controlled vocabulary retrievable from many entry points while remaining canonical in its output.

Structural Signature

Sig role-phrases:

  • the non-preferred surface form — a synonym, abbreviation, alternate spelling, colloquial phrase, or superseded name a user might type ("heart attack", "AZT")
  • the canonical descriptor — the one form with full indexing and display privileges the alias points to ("Myocardial Infarction", "Zidovudine")
  • the many-to-one routing relation — many entry terms map to one descriptor; the descriptor merely lists them as metadata and never back-routes
  • the silent routing contract — the search interface expands a query on the alias to the descriptor without surfacing the alias as a competing answer
  • the non-indexing rule — an alias accumulates no records of its own; no resource is indexed under it as a heading
  • the input/output two-surface split — surface variation is absorbed at the input surface while the indexed output surface stays exactly the canonical set
  • the alias-curation discipline — the maintainer adds newly popular phrases, retires confusing rare ones, and points renamed forms forward
  • the reach-without-bloat guarantee — alias-layer edits raise reachability while provably leaving the indexed descriptor space invariant, because the route runs one way only
  • the active-versus-sunset role distinction — an entry-term alias never was preferred and routes inward to a live descriptor, unlike a retired term routing forward to a successor
  • the non-indexing limitation — the non-indexing-and-curation discipline is meaningful only where there is an indexed corpus to keep coherent; the bare routing reduces to many-to-one function_mapping plus a canonical-form policy off-substrate

What It Is Not

  • Not a symmetric synonym. The relation is many-to-one and asymmetric: many entry terms route to one canonical descriptor, and the descriptor merely lists them as metadata rather than routing back. Alias and descriptor are not interchangeable equals — one indexes and displays, the other is absorbed silently and never back-routed. A symmetric synonymy relation would make them co-equal members of one class; entry-term aliasing is status-unequal and directionally committed, which is exactly the line between alias-as-routing-contract and synonymy-as-equivalence.
  • Not an indexing target. An entry term accumulates no records of its own: no article is indexed under "heart attack" as a heading, even though searches on it expand to "Myocardial Infarction." Its standing is pure routing metadata at the input surface. An alias that has somehow accreted its own indexed content has breached the non-indexing rule — wrongly promoted to a competing heading, splitting literature that should have funneled to one descriptor.
  • Not a retired or superseded term. An entry-term alias was never a preferred form and routes inward to a live descriptor (the active case). A renamed descriptor's old preferred form routes forward to its successor (the sunset case). Both are non-indexing routes, but their direction and provenance differ; conflating them loses the distinction between absorbing surface variation and retiring a former canonical form.
  • Not a distinct concept deserving its own descriptor. An entry term is a curated non-preferred surface form absorbed at the input surface, not a topic in its own right. Promoting every colloquial phrase, abbreviation, or misspelling to a descriptor is the combinatorial bloat the two-surface split exists to prevent — surface variation belongs on the alias layer (governed for reach), while the descriptor set (governed for coherence) stays stable. Meeting a reachability demand by minting a descriptor pushes variation onto the wrong surface.

Scope of Application

The entry term alias lives within controlled-vocabulary practice — the indexing subfields where a curated non-preferred surface form routes many-to-one, silently and non-indexing, to a canonical descriptor, governing reach at the input surface while the indexed output stays canonical; its reach is within that substrate (the DNS-CNAME, symlink, SKU-variant, ORCID-merge, and "did you mean" cousins are co-instances of the parent — many-to-one function_mapping plus a canonical-form policy — and lack the non-indexing rule and two-surface coherence guarantee, which have no analogue where there is no indexed corpus to keep coherent).

  • Biomedical literature indexing (MeSH) — the home: entry terms / "see from" references route variant phrasings ("heart attack" → "Myocardial Infarction", "AZT" → "Zidovudine") to the canonical descriptor, expanded silently in PubMed search.
  • Library cataloging (LCSH UF entries) — "Used For" fields on authority records route a non-preferred form ("Automobiles") to its heading ("Motor vehicles") without the alias accruing its own index entries.
  • Domain thesauri (Getty AAT) — alternate labels routing variant terms to the preferred form within an art-and-architecture vocabulary.
  • SKOS-based controlled vocabularies — skos:altLabel carrying the non-preferred forms that route to a concept's preferred label, the same input-surface absorption in a linked-data model.
  • Vocabulary alias curation — the maintenance discipline itself: adding newly popular phrases to raise reach, retiring confusing rare aliases, and pointing a renamed descriptor's old form forward to its successor, all leaving the indexed space invariant.

Clarity

Naming the entry term alias makes legible that a non-preferred surface form is subordinate routing metadata, not a synonym in the ordinary symmetric sense. Without the concept, "heart attack" and "Myocardial Infarction" look like two interchangeable names for one thing, and it is unclear which should carry index entries or why a search on one returns the other. Seeing the alias as a directed, non-indexing bridge dissolves that: the relation is many-to-one and asymmetric — many entry terms route to one canonical descriptor, and the descriptor merely lists them rather than routing back — so the alias and the descriptor are not equals. One gets indexed and displayed; the other is absorbed silently at the input surface and never accumulates references of its own. The recurring question stops being "are these the same concept?" and becomes "is this surface form a curated alias that should route inward, or a distinct concept that deserves its own descriptor?" That is the line between synonymy-as-equivalence and alias-as-routing-contract, and the concept is what lets a vocabulary maintainer hold it.

The concept also makes legible the dilemma that alias routing exists to dissolve, and where each horn fails. Without curated aliases, the maintainer must either mint a descriptor for every colloquial phrase, abbreviation, and misspelling — combinatorial bloat that destabilizes the descriptor set — or leave users who know a concept only by its common name unable to reach it — silent recall failure. Recognizing the entry term as the load-bearer for surface variation separates the two surfaces cleanly: input absorbs many forms, output stays canonical. The practitioner can then ask the maintenance questions the mechanism actually turns on: has a new colloquial phrase gained enough traction to warrant adding it as an entry term? Has an existing alias become so rare it now generates more confusion than recall and should be retired? And — the boundary against its sibling case — when the canonical descriptor is itself renamed, its old preferred form becomes an entry term routing forward to the successor, which is the sunset variant of routing, distinct from an alias that was never a preferred form and routes inward to a live descriptor. The named concept is what keeps those two non-canonical roles from being confused.

Manages Complexity

A controlled vocabulary faces two demands that pull in opposite directions: its descriptor set must stay small and stable so indexing and retrieval remain coherent, yet it must be reachable by every surface form — synonym, abbreviation, colloquialism, misspelling, superseded name — that a user might actually type, a set that is open-ended and forever growing. Holding both in one inventory is intractable; the descriptor list would have to be simultaneously minimal and exhaustive. The entry term alias resolves the tension by splitting the problem across two surfaces tied by a single asymmetric routing relation. All the unbounded surface variation is absorbed at the input surface as non-indexing aliases that route many-to-one to canonical descriptors; the output surface — what gets indexed, displayed, and counted — stays exactly the stable descriptor set, untouched by how many aliases point inward. The maintainer therefore reasons about two cleanly separated things rather than one overloaded one: a canonical set governed for coherence, and an alias inventory governed for reach, with the routing contract guaranteeing the second never perturbs the first. Adding a newly popular phrase, retiring a confusing rare one, or pointing a renamed descriptor's old form forward to its successor are all local edits to the alias layer that leave the indexed space invariant. The impossible "small yet exhaustively reachable vocabulary" reduces to a fixed canonical set plus a curated, directionally committed alias inventory that carries the variation load on its own.

Abstract Reasoning

Treating the alias as a directed, non-indexing, many-to-one routing bridge — variation absorbed at the input surface while the output stays canonical — lets the vocabulary maintainer and the search system draw several concrete inferences.

Diagnostic — read a routing or status fault off a retrieval symptom. When users who know a concept only by a common name ("heart attack," "AZT") retrieve nothing though the descriptor is well populated, infer a missing entry term — the surface form was never curated as an alias, so the input surface failed to absorb it and no silent expansion fired. The recall gap localizes to the alias inventory, not the descriptor. The opposite symptom points elsewhere: when a non-preferred form has somehow accumulated its own indexed records, infer the non-indexing rule was breached — the alias was wrongly promoted to a competing heading rather than kept as pure routing metadata, splitting the literature that should have funneled to one descriptor. And when a query expands to a descriptor that no longer exists or has been renamed, infer the alias was left pointing at a stale canonical form — a maintenance lapse from a descriptor rename that did not update the inward route. The move runs from a retrieval symptom (unreachable concept, alias accreting content, expansion to a dead descriptor) to the specific fault (missing alias, broken non-indexing rule, stale routing target) that produced it.

Interventionist — predict what an alias edit moves, and what it leaves invariant. The maintainer reasons forward from an alias-layer edit to its effect, and the defining prediction is what stays the same: because the routing relation is asymmetric and the alias is non-indexing, adding a newly popular phrase as an entry term raises reach — searches on that phrase now expand silently to the descriptor — while the indexed and displayed space is untouched, no descriptor gained or lost. Retiring a confusing rare alias removes one input route but again leaves the canonical set invariant. Pointing a renamed descriptor's old preferred form forward to its successor preserves backward reachability without reviving the old form as a heading. The general inference: edits to the alias inventory are local to the input surface and provably cannot perturb the output surface, because the contract routes one way only — so the maintainer can change reach freely without auditing the indexed space, a guarantee that follows directly from the directional, non-indexing commitment. Each edit's effect is checkable by querying the affected surface form and confirming it lands on the intended descriptor while the descriptor's own record is unchanged.

Boundary-drawing — alias-routing versus symmetric synonymy, and the two non-canonical roles. The defining adjudication the concept forces is whether a surface form is a curated alias that should route inward or a distinct concept that deserves its own descriptor — the line between alias-as-routing-contract and synonymy-as-equivalence. The two are not interchangeable: a symmetric synonymy relation would make alias and canonical equal members of one class, but entry-term aliasing is asymmetric and status-unequal — one form indexes and displays, the other is absorbed silently and never back-routed — so reasoning about an alias as if it were a co-equal synonym mis-models the routing direction and the indexing privilege. A second boundary the concept draws separates the two non-canonical roles a form can occupy in a maintained vocabulary: an entry-term alias was never a preferred form and routes inward to a live descriptor (the active case), whereas a renamed descriptor's superseded form routes forward to its successor (the sunset case) — both are non-indexing routes, but their direction and provenance differ, and conflating them loses the distinction between absorbing surface variation and retiring a former canonical form. Deciding which role a non-preferred form plays is exactly what the named concept keeps from being confused.

Two-surface factoring — reach and coherence governed separately. A structural inference follows from splitting the vocabulary across two surfaces tied by one asymmetric relation: the open, ever-growing set of surface forms is governed for reach in the alias layer, while the descriptor set is governed for coherence in the output layer, and the routing contract guarantees the first never perturbs the second. Reasoning from this factoring, the maintainer treats "small yet exhaustively reachable" not as a single impossible target on one list but as two cleanly separated objectives on two lists — so the correct response to a new colloquial phrase is an alias-layer edit (raise reach) that by construction leaves the indexed space invariant (preserve coherence), and any proposal that would meet a reachability demand by minting a descriptor is recognizable as pushing surface variation onto the wrong surface, reintroducing the bloat the two-surface split exists to prevent.

Knowledge Transfer

Within controlled-vocabulary practice the concept transfers as mechanism, with its asymmetric-routing and two-surface diagnostics intact. The entry-term-alias discipline — a curated inventory of non-preferred surface forms that route many-to-one, silently and non-indexing, to a canonical descriptor, governing reach at the input surface while the indexed output stays canonical — carries across the indexing family without translation: MeSH entry terms / "see from" references (the home case: "heart attack" → "Myocardial Infarction", "AZT" → "Zidovudine"), LCSH UF ("Used For") entries on authority records, the AAT's alternate labels, and SKOS altLabel. A maintainer reads the same diagnostics (a concept unreachable by a common name means a missing entry term; an alias that has accreted its own indexed records means the non-indexing rule was breached; an expansion to a renamed descriptor means a stale routing target) and the same interventions (add a popular phrase to raise reach with the indexed space provably invariant; retire a confusing rare alias; point a renamed descriptor's old form forward to its successor) in each. These are co-instances of one alias-routing discipline, not analogies, because each absorbs surface variation at the input surface through a directionally committed, status-unequal route that by construction cannot perturb the canonical set.

Beyond controlled vocabularies the transfer splits, and both halves should be reported honestly. There is a genuine shared abstract mechanism — case (B) — wherever an asymmetric many-to-one route resolves alternate addresses to one canonical address: DNS CNAMEs (www.example.com → example.com), filesystem symlinks, shell aliases, ORCID merged records and DOI redirects (legacy ID → current), e-commerce variant-search routing ("kleenex" → "facial tissue"), and search-engine "did you mean" reformulation are co-instances of "many surface forms route silently to one canonical form, the alias non-equal and non-back-routing," not mere resemblances. The portable content there is the parent: many-to-one function_mapping (the resolution relation) plus a canonical-form preference policy (which representative is privileged) — and that parent, together with the asymmetry that distinguishes it from symmetric equivalence_relation synonymy, is what should be carried when the lesson is needed across these substrates. What does not travel out, even to the genuine cousins, is the home-bound cargo: the non-indexing rule specifically (an entry term accumulates no content of its own — meaningful where there is an indexed corpus to keep coherent, but with no analogue in a DNS zone, which has nothing to "index"), the input-surface/output-surface factoring tuned to the small-yet-exhaustively-reachable vocabulary problem, the MeSH/LCSH entry-term and UF curation, and the active-versus-sunset role distinction (an entry-term alias never was a preferred form and routes inward to a live descriptor, whereas a retired term routes forward to a successor — a within-vocabulary bookkeeping distinction). So even where the routing mechanism genuinely recurs, the named entry-term-alias concept — with its non-indexing discipline and two-surface coherence guarantee — does not; calling a DNS CNAME an "entry term alias" borrows the asymmetric-routing shape while dropping the non-indexing and curation discipline that give the original its force. The cross-substrate lesson belongs to the function_mapping-plus-canonical-policy parent, not to the cataloging concept as named (see Structural Core vs. Domain Accent).

Examples

Canonical

In MeSH, the descriptor "Myocardial Infarction" carries the entry term "Heart Attack" (among others) in its record. No article is ever indexed under "Heart Attack" as a heading — the indexed, displayed, counted form is always "Myocardial Infarction." But when a user types "heart attack" into PubMed, the Automatic Term Mapping engine silently expands the query to the descriptor and its tree, retrieving the controlled corpus. The user sees results, not the routing. The relation is strictly one-directional: "heart attack" points to "Myocardial Infarction," but the descriptor's record merely lists "Heart Attack" as one of several synonyms and never routes back out to it. The same pattern maps "AZT" and "Retrovir" to the descriptor "Zidovudine."

Mapped back: "Heart Attack" is the non-preferred surface form; "Myocardial Infarction" is the canonical descriptor. PubMed's silent query expansion is the silent routing contract; the fact that no record indexes under "Heart Attack" is the non-indexing rule. That the descriptor lists the term but never back-routes is the many-to-one routing relation.

Applied / In Practice

A MeSH maintainer at the National Library of Medicine curates the alias inventory as biomedical language shifts. When "COVID-19" surged in usage in early 2020, the maintainers introduced the descriptor and attached entry terms such as "2019-nCoV Disease" and "SARS-CoV-2 Infection" so that clinicians searching by any current phrasing reach the same indexed literature; the annual MeSH revision cycle is where such alias-layer edits are absorbed. Crucially, adding these entry terms raised reach — more surface forms now expand inward — without minting rival descriptors that would fragment the indexed corpus. When a descriptor is renamed across revisions, its former preferred form is retained as an entry term routing forward to the successor, preserving backward reachability for citations that used the old heading.

Mapped back: Attaching new synonyms as usage shifts is the alias-curation discipline, and doing so without new descriptors is the reach-without-bloat guarantee riding on the input/output two-surface split (reach governed at input, coherence at output). Retaining a renamed form to route forward is the active-versus-sunset role distinction — the sunset case routing to a successor, not inward to a live descriptor.

Structural Tensions

T1: Reach versus precision (every alias widens the door and can blur it). Adding an entry term is pure gain on the recall axis: a user who knows the concept only as "heart attack" now reaches "Myocardial Infarction," and the indexed space is provably untouched. But reach and precision pull against each other at the input surface. A colloquial or abbreviated form can be claimed by more than one descriptor — an ambiguous acronym, a lay phrase that spans two clinical concepts — so an over-generous alias inventory routes a query to a descriptor the user did not mean, or forces the search engine to expand into a disjunction the user cannot see. The curation rule itself concedes this: rare forms that "generate more confusion than recall" are retired. So the alias layer is not free to grow without bound; each addition trades recall gained against precision risked. Diagnostic: Does this surface form route unambiguously to one descriptor, or could it belong to two — such that adding it raises reach at the cost of misrouting queries?

T2: Silent routing versus hidden substitution (seamlessness that conceals a reinterpretation). The routing contract is silent — PubMed's Automatic Term Mapping expands "heart attack" to "Myocardial Infarction" without surfacing the alias as a competing answer, and the user sees results, not the route. That invisibility is the mechanism's charm: users arrive at one place however they name the concept. But silence also means the system reinterprets the user's term without telling them, and where the alias is a loose fit — a lay phrase mapped to a narrower or broader descriptor than the user intended — the substitution is exactly what the user needed to know and never learns. The same silence that smooths retrieval hides the possibility that the vocabulary understood the query differently than the searcher did. Diagnostic: If the user could see that their term was silently expanded to this descriptor, would they endorse the substitution — or does the silence mask a mismatch they would have caught?

T3: Subordinate alias versus emerging concept (the promotion boundary the non-indexing rule defends). An entry term is held subordinate by rule: it indexes nothing, displays nothing, accumulates no records of its own, and never back-routes. This is what keeps the descriptor set small and stable. But language does not respect the demotion — a form curated as a mere synonym can, as the literature shifts, come to mark a genuinely distinct concept that deserves its own descriptor, and holding it as pure routing metadata then suppresses a real distinction and funnels two literatures into one heading. The concept's own defining adjudication is exactly this branch: curated alias that routes inward, or distinct concept that earns a descriptor? The non-indexing rule is a discipline held against the drift, and the maintainer must decide when a subordinate form has outgrown its subordination. Diagnostic: Is this form still a surface variant of one canonical concept, or has usage split it into a distinct topic that would fragment retrieval if kept as a non-indexing alias?

T4: One non-indexing surface versus two provenances (active-inward and sunset-forward look identical). Operationally, an entry-term alias and a renamed descriptor's superseded form are indistinguishable: both are non-preferred, both index nothing, both route a query silently to a canonical descriptor. Yet their provenance and direction differ — the active alias never was preferred and routes inward to a live descriptor ("AZT" → "Zidovudine"), while the sunset form once was the heading and routes forward to a successor after a rename. The mechanism gives them the same mechanical shape while demanding they be governed differently: the active case is absorbing surface variation, the sunset case is retiring a former canonical form and preserving backward reachability for old citations. Conflating them loses that difference, and a maintainer who cannot read provenance off an identical-looking route will mis-handle one as the other. Diagnostic: Was this non-preferred form ever the preferred descriptor — routing forward to a successor — or never preferred, routing inward to a live descriptor it merely names?

T5: Currency versus stability (the two surfaces run on different clocks). The design deliberately splits the vocabulary so the descriptor set stays fixed while the alias layer chases usage. But "chases usage" is an unbounded, ongoing obligation: when "COVID-19" surged in early 2020, maintainers had to attach "2019-nCoV Disease" and "SARS-CoV-2 Infection" as entry terms so clinicians using any current phrasing reached the same literature, and the annual revision cycle is where such edits land. The alias layer must therefore move at the speed of language while the descriptor set holds still by design — two surfaces running on different clocks, with the maintainer absorbing the friction between them. Lag on the alias clock produces silent recall failure for the newest phrasings; over-eager addition reintroduces the ambiguity of T1. Stability at the output is bought with perpetual motion at the input. Diagnostic: Is the alias inventory current with how users actually name this concept now, or has language moved while the descriptor's fixity let the alias layer fall behind?

T6: Autonomy versus reduction (its own curatorial concept or the indexing instance of many-to-one routing). "Entry term alias" is a fully specified controlled-vocabulary artifact, with home machinery: MeSH "see from" references, LCSH UF fields, SKOS altLabel, the non-indexing rule, and the two-surface reach-without-bloat guarantee. Yet its portable core — many surface forms route silently, asymmetrically, one-way to a canonical form — is not proprietary: DNS CNAMEs, filesystem symlinks, shell aliases, DOI redirects, and "did you mean" reformulation are genuine co-instances of the parent, many-to-one function_mapping plus a canonical-form preference policy. What does not travel is the home-bound cargo — the non-indexing rule (a DNS zone has nothing to index), the input/output factoring tuned to the small-yet-reachable-vocabulary problem, and the active-versus-sunset bookkeeping. The tension is between a named cataloging discipline that earns its own curation rules and the recognition that its cross-substrate lesson already belongs to the routing-plus-canonical-policy parent. Diagnostic: Resolve toward the parent (many-to-one function_mapping plus canonical-form policy) when asking what carries to CNAMEs, symlinks, or redirects; toward the named alias when governing a MeSH entry term's non-indexing status and curation in situ.

Structural–Framed Character

The entry term alias sits on the framed side of the spectrum — best read as framed-leaning: an evaluatively neutral routing mechanism that is nonetheless an artifact of a curatorial practice and packaged by named cataloging institutions. On evaluative_weight it is the one criterion that points structural: a term routing inward to a descriptor is neither good nor bad, and "entry term alias" convicts nothing — it names a piece of routing metadata, not a verdict. But the other four criteria pull framed. On human_practice_bound it is framed: the concept's distinctive commitments dissolve the moment the practice is removed — the entry's own limitation phrase says the non-indexing-and-curation discipline "is meaningful only where there is an indexed corpus to keep coherent," and stripped of the maintained vocabulary the mechanism "reduces to many-to-one function_mapping plus a canonical-form policy." There is no observer-free entry-term aliasing the way there is observer-free enzyme kinetics; the artifact exists because a maintainer curates it. On institutional_origin it is strongly framed: the concept is furniture of specific cataloging traditions — MeSH "see from" references, LCSH UF fields, the Getty AAT, SKOS altLabel, the annual NLM revision cycle — a designed convention of librarianship, not a fact of nature. On vocab_travels it is framed: the operative vocabulary — descriptor, entry term, non-indexing rule, two-surface factoring, active-versus-sunset — is pinned to indexed-corpus practice and, as the entry stresses, has "no analogue in a DNS zone, which has nothing to index."

The portable structural skeleton is the asymmetric many-to-one routing relation — many surface forms resolving silently, one-way, to a privileged canonical form — which the entry names precisely as the parent it instantiates: many-to-one function_mapping plus a canonical-form preference policy (distinguished from symmetric equivalence_relation synonymy by the asymmetry). That parent is what reaches across DNS CNAMEs, filesystem symlinks, shell aliases, DOI redirects, and "did you mean" reformulation as genuine co-instances; the named entry-term-alias concept — with its non-indexing rule, reach-without-bloat two-surface guarantee, and active/sunset bookkeeping — is exactly the domain-accented cargo that does not travel, which is why the import_vs_recognize reading is framed: calling a CNAME an "entry term alias" borrows the routing shape while dropping the curatorial discipline that gives the original its force. Its character: an evaluatively neutral routing mechanism whose portable core is the asymmetric many-to-one function_mapping-plus-canonical-policy skeleton it instantiates, but constituted by a curatorial practice and defined inside named cataloging institutions, leaving it framed-leaning rather than a free-floating prime.

Structural Core vs. Domain Accent

This section decides why the entry term alias is a domain-specific abstraction and not a prime, by separating the thin asymmetric-routing skeleton it instantiates from the cataloging-curation machinery that constitutes the named concept.

What is skeletal (could lift toward a cross-domain prime). Strip the vocabulary away and a thin relational structure survives: many surface forms resolve silently, one-way, to a single privileged canonical form — the alias non-equal to the canonical, and never back-routing. The portable pieces are abstract — a set of alternate addresses, a canonical address, a directional resolution relation, and the asymmetry that keeps the alias subordinate. That structure is genuinely substrate-spanning: it recurs as DNS CNAMEs (www.example.com → example.com), filesystem symlinks, shell aliases, ORCID merged records and DOI redirects (legacy ID → current), e-commerce variant search, and "did you mean" reformulation — genuine co-instances, not resemblances. Precisely because it recurs as mechanism, it is carried by the parent the entry names: many-to-one function_mapping (the resolution relation) plus a canonical-form preference policy (which representative is privileged), distinguished from symmetric equivalence_relation synonymy by exactly that asymmetry. But this is the core the entry term alias shares, not what makes it distinctive.

What is domain-bound. Almost everything that makes the concept an entry term alias in particular is controlled-vocabulary furniture that does not survive extraction. The surface forms are non-preferred descriptors (synonyms, abbreviations, superseded names); the canonical form is an indexed, displayed descriptor; and the load-bearing rule is the non-indexing rule — an entry term accumulates no records of its own, no resource is indexed under it as a heading. On this rides the input-surface/output-surface factoring tuned to the small-yet-exhaustively-reachable-vocabulary problem (reach governed at input, coherence at output, with a reach-without-bloat guarantee), the active-versus-sunset bookkeeping (an entry-term alias never was preferred and routes inward to a live descriptor, whereas a renamed descriptor's old form routes forward to a successor), and the institutional apparatus — MeSH "see from" references, LCSH UF fields, SKOS altLabel, the annual NLM revision cycle. These are the worked vocabulary, the instruments, and the empirical cases the practice actually operates. The decisive test the entry states outright: the non-indexing-and-curation discipline is meaningful only where there is an indexed corpus to keep coherent — a DNS zone has nothing to index. Remove the indexed corpus and the curator, and the concept reduces to the bare parent (many-to-one function mapping plus a canonical-form policy), a looser thing with none of the non-indexing or two-surface machinery.

Why this does not clear the prime bar. A prime's vocabulary travels and its cross-domain transfer is recognition of the same mechanism, not analogy. The entry term alias's transfer is bimodal. Within controlled-vocabulary practice it travels intact as mechanism — MeSH entry terms, LCSH UF entries, the Getty AAT's alternate labels, and SKOS altLabel are co-instances of one alias-routing discipline, so the asymmetric-routing diagnostics, the non-indexing rule, the two-surface interventions, and the active/sunset distinction carry without translation. Beyond controlled vocabularies the routing mechanism still genuinely recurs — but that is precisely the point against prime-hood: what recurs in CNAMEs, symlinks, and redirects is the parent (many-to-one function_mapping plus a canonical-form policy), not "entry term alias" with its non-indexing rule and curation discipline, which have no analogue where there is no corpus to keep coherent. Calling a DNS CNAME an "entry term alias" borrows the asymmetric-routing shape while dropping exactly the cargo that gives the original its force. So when the bare structural lesson is needed cross-substrate — alternate addresses resolve one-way to a canonical one — it is already carried, in more general form, by the parent the entry instantiates. The cross-domain reach belongs to that function_mapping-plus-canonical-policy parent; "entry term alias," as named — the non-indexing rule, the reach-without-bloat two-surface guarantee, the active/sunset bookkeeping — is cataloging furniture that should stay home, which is why it clears the domain-specific bar for controlled-vocabulary practice but not the prime bar.

Relationships to Other Abstractions

Local relationship map for Entry Term AliasParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Entry Term AliasDOMAINDomain-specific abstraction: Alternative label — is a kind ofAlternativelabelDOMAINDomain-specific abstraction: Preferred Term — is part ofPreferred TermDOMAIN

Current abstraction Entry Term Alias Domain-specific

Parents (1) — more general patterns this builds on

  • Entry Term Alias is a kind of Alternative label Domain-specific

    Entry Term Alias is the indexed-corpus species of Alternative Label with a strict non-indexing rule and a silent query-expansion routing contract.

Children (1) — more specific cases that build on this

  • Preferred Term Domain-specific is part of Entry Term Alias

    The preferred-term system contains the non-preferred entry-term routes that preserve backward search while obligating one form for forward indexing.

Hierarchy paths (9) — routes to 4 parentless roots

Not to Be Confused With

  • Symmetric synonym / equivalence relation. Two interchangeable, co-equal names for one thing, either substitutable for the other. An entry term alias is asymmetric and status-unequal: it routes one-way to a canonical descriptor that merely lists it and never back-routes; one form indexes and displays, the other is absorbed silently. Tell: are the two forms interchangeable equals (synonymy), or is one subordinate routing metadata pointing at a privileged descriptor (entry term alias)?
  • The canonical descriptor (preferred term). The one form with full indexing and display privileges ("Myocardial Infarction") that the alias points to. The entry term alias is the non-preferred form ("heart attack") absorbed at the input surface. Confusing them inverts the routing direction and the indexing privilege. Tell: is it the form under which records are indexed and displayed (descriptor), or the surface variant that silently expands to it (alias)?
  • Retired / superseded term (the sunset case). A form that once was the preferred descriptor and now routes forward to its renamed successor. An entry term alias never was preferred and routes inward to a live descriptor. Both are non-indexing routes, but their direction and provenance differ. Tell: was this form ever the canonical heading, now pointing to a successor (retired term), or never preferred, pointing inward to a live descriptor it merely names (entry term alias)?
  • A distinct concept deserving its own descriptor. A surface form that marks a genuinely separate topic and should be promoted to an indexed heading. Keeping such a form as a non-indexing alias suppresses a real distinction; promoting every colloquialism to a descriptor is the bloat the two-surface split prevents. This is the concept's core adjudication. Tell: is the form a surface variant of one canonical concept (alias, route inward), or a distinct topic that would fragment retrieval if not given its own descriptor?
  • DNS CNAME / symlink / redirect (genuine cousins). Asymmetric many-to-one routes resolving alternate addresses to one canonical address in computing. These are real co-instances of the parent (many-to-one function_mapping plus canonical-form policy), but they lack the non-indexing rule and two-surface coherence guarantee — a DNS zone has nothing to index. Tell: is there an indexed corpus whose coherence the non-indexing discipline protects (entry term alias), or bare address resolution with no corpus (CNAME/symlink)? (Treated more fully in Structural Core vs. Domain Accent.)
  • "Did you mean" / query reformulation. A search engine suggesting or silently substituting a corrected/expanded query. It shares the input-surface routing shape but is typically a ranked guess over a full-text index, not a curated, directionally committed alias in a controlled vocabulary with a stable descriptor set. Tell: is the route a curated entry in a maintained authority record (entry term alias), or an algorithmic reformulation over unindexed free text ("did you mean")?

Neighborhood in Abstraction Space

Entry Term Alias sits in a sparse region of the domain-specific corpus (73rd percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Surface Form & Underlying Structure (23 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12