Precoordinated Heading¶

Fuse topic, place, period, and form into one canonical subject string at indexing time so users retrieve by matching a whole browsable label, trading expressiveness and easy schema evolution for that browsability.

Core Idea¶

A precoordinated heading is a classification design choice in which multiple dimensions of description — topic, geographic qualifier, chronological subdivision, form — are combined into a single composite label at indexing time, before any search has been issued, rather than being assembled from separate facets by the user at query time (postcoordination). The heading is a fixed string with internal grammar: in LCSH, "United States — History — Civil War, 1861–1865 — Personal narratives, Confederate" combines a geographic entity, a subject, a date range, and a form subdivision into one canonical string that the cataloger constructs once, records in the authority file, and the user matches as a whole. The structural commitments are a fixed compositional grammar specifying which element types may appear in which positions, an authority file of valid pre-built combinations, and a single-string match at retrieval rather than multi-facet intersection.

The design front-loads combination cost onto catalogers and schema designers so that users can navigate by matching single strings — and so that headings can be arranged alphabetically on a card catalog or printed shelf list without any composition machinery on the retrieval side. The trade is that the heading space is enumerated rather than constructed: new combinations require new headings, rare combinations may simply not exist in the authority file, and when the schema evolves the enumerated headings must be re-cataloged rather than re-combined. The opposite design choice is postcoordination — keeping facets separate and combining them at query time — which is more expressive and more scalable at the cost of browsability. LCSH is the canonical precoordinated vocabulary; OCLC FAST and faceted thesauri represent the postcoordinated alternative applied to the same underlying descriptive territory. The same eager-versus-lazy tension appears in database design as the choice between a materialized denormalized join (precoordination) and normalized tables combined at query time (postcoordination).

Structural Signature¶

Sig role-phrases:

the composite label — a single canonical string fusing multiple description dimensions (topic, geographic, chronological, form) into one heading
the fixed compositional grammar — the rule specifying which element types may occupy which positions, giving each heading its canonical form
the eager combination at indexing time — the dimensions are combined once by the cataloger, before any search, rather than assembled by the user at query time
the authority file — the store of valid pre-built combinations against which a heading is recorded and matched
the single-string match — retrieval is whole-string matching, with no multi-facet intersection machinery on the retrieval side
the enumerated heading space — only constructed combinations exist, so rare or novel intersections may simply have no heading (the characteristic limitation)
the relocated combination cost — the trade-structure: browsability gained, expressiveness and schema-evolution maintenance lost, all read off the one eager-versus-lazy axis

What It Is Not¶

Not an irreducible label. A heading like "United States — History — Civil War, 1861–1865 — Personal narratives, Confederate" only looks atomic; it is a decision to fuse topic, place, period, and form at indexing time, with postcoordination — leaving the facets separate for the user to intersect at query time — held in view as the live alternative. The defining fact is when the dimensions were combined, not that the result reads as one string.
Not a free-text string. Each heading obeys a fixed compositional grammar specifying which element types may occupy which positions, and is authority-controlled against a store of valid pre-built combinations. Treating it as an arbitrary label misses the grammar and the authority file that give it its canonical form.
Not strictly better (or worse) than postcoordination. It is one end of an eager-versus-lazy trade, not a winner: precoordination gains browsability (the enumerated strings sort and shelve alphabetically with no retrieval-side composition) while losing expressiveness and schema-evolution maintenance. The combination cost does not vanish — it is relocated onto catalogers and schema designers — so the choice is a trade-structure, not an improvement.
Not a coverage gap when a combination has no heading. A search that finds no heading for an unusual topic-place-form intersection is not an indexing oversight but the structural signature of enumerating combinations in advance: the heading was never built because the space is enumerated, not constructed. The fix is a design lever (shift toward facets), not a missing catalog record.
Not the general eager/lazy pattern itself. Precoordination instantiates precomputation-versus-deferral (materialized denormalized join versus normalized tables combined at query time), but its compound-subject-heading machinery — the grammar of subject strings, the authority file, card/shelf-list browsability, the re-cataloging burden — stays home-bound. The substrate-spanning trade belongs to the eager-versus-materialization parent, which is the right level to lift it.

Scope of Application¶

The precoordinated heading lives across the classification-and-retrieval subfields of library and information science — one substrate, compositional descriptive vocabularies for retrieval; the substrate-spanning eager-versus-lazy trade (materialized joins, compiled execution, prefabricated products) belongs to the precomputation-versus-deferral parent, not to compound subject headings.

Subject cataloging — LCSH headings like "United States — History — Civil War, 1861–1865 — Personal narratives, Confederate" are constructed once at indexing time, with OCLC FAST and faceted thesauri the postcoordinated alternative over the same descriptive territory.
Classified shelving systems — Dewey and Library of Congress call numbers fuse class, region, period, and form into a single browsable string with no composition machinery on the retrieval side.
Enumerated bibliographic taxonomies — pre-Internet abstracting services and hierarchical subject-code schemes mint composite codes once and match them whole.

Clarity¶

Naming a heading as precoordinated makes explicit a choice that a finished subject string otherwise conceals: when its dimensions were combined. "United States — History — Civil War, 1861–1865 — Personal narratives, Confederate" looks like an irreducible label, but the precoordination concept reveals it as a decision to fuse topic, place, period, and form at indexing time, with the alternative — postcoordination, leaving the facets separate for the user to intersect at query time — held in view as a live option rather than an unconsidered default. Once the catalog designer can name where combination happens, the trade-offs become askable instead of inherited: precoordination buys browsability (the headings file alphabetically with no composition machinery on the retrieval side) at the cost of expressiveness (the heading space is enumerated, so rare or novel combinations may simply not exist) and maintenance (when the schema evolves, enumerated headings must be re-cataloged rather than re-combined).

The concept also localizes a class of failures that would otherwise look like gaps in coverage. A search that finds no heading for an unusual topic-place-form combination is not necessarily an indexing oversight; the precoordination frame diagnoses it as a structural consequence of enumerating combinations in advance, and points to the design lever — shift the cost of combination from cataloger to user by moving toward facets. It distinguishes the fixed compositional grammar (which element types may occupy which positions) that gives each heading its canonical form from a free-text label, and reframes "what heading does this resource need?" as the prior question the design actually turns on: which combinations are worth building once and citing as whole strings, and which should be left for the user to assemble?

Manages Complexity¶

For the user and the retrieval system, a precoordinated heading collapses what would otherwise be a multi-dimensional assembly problem into a single act of string-matching. A description spanning topic, place, period, and form could be reached only by intersecting four facet selections at query time — composition machinery the retrieval side must implement and the user must operate — but precoordination performs that combination once, at indexing time, and records the result as one canonical string. The user navigates by matching that whole string, and the headings, being fixed strings, file alphabetically on a card or shelf list with no intersection logic anywhere on the retrieval side. The sprawling space of possible cross-cutting queries is tamed, from the user's vantage, into a flat browsable list. The compression is real but its location is the point: the cost of combination has not vanished, it has been moved off the retrieval side and front-loaded onto catalogers and schema designers, who must construct and authority-control the composite strings in advance.

What the catalog designer reads off the precoordination choice, then, is not a single outcome but a fixed trade-structure that makes the design's qualitative behavior predictable without re-litigating each heading. Three parameters move together off the one decision of when combination happens: browsability (precoordination wins — the enumerated strings sort and shelve directly), expressiveness (precoordination loses — only constructed combinations exist, so a rare topic-place-form intersection may simply have no heading), and maintenance (precoordination loses — when the schema evolves, the enumerated headings must be re-cataloged rather than re-combined). The designer reads each consequence off the single eager-versus-lazy axis rather than discovering it per case. The same axis localizes a class of apparent failures: a query that finds no heading for an unusual combination is read not as an indexing oversight but as the structural signature of enumerating combinations in advance, and the design lever follows immediately — shift toward facets to move the combination cost back to the user. The open question "what heading does each resource need?" reduces to the prior, bounded one the design actually turns on: which combinations are worth building once and citing as whole strings (frequent, browsable, stable), and which should be left for the user to assemble at query time (rare, novel, schema-volatile) — a single sort of the combination space along the eager/lazy line, with browsability, expressiveness, and maintenance all read off where a heading lands on it.

Abstract Reasoning¶

The concept's foundational move is a when-did-combination-happen inference applied to a finished heading. "United States — History — Civil War, 1861–1865 — Personal narratives, Confederate" looks like an irreducible label, but the analyst reads it as a decision to fuse topic, place, period, and form at indexing time, with postcoordination — leaving the facets separate for the user to intersect at query time — held in view as the live alternative rather than an unconsidered default. The reasoning runs from the composite string back to the design choice that produced it, and it relocates the combination cost: the cost has not vanished but been moved off the retrieval side and front-loaded onto catalogers and schema designers. This is the eager-versus-lazy axis instantiated in classification, and naming where on it a heading sits is what makes the rest of the reasoning available.

From that single axis the analyst draws a trade-structure inference: three parameters move together off the one decision, so the design's qualitative behavior is predicted without re-litigating each heading. Precoordination wins browsability (the enumerated strings sort and shelve alphabetically with no composition machinery on the retrieval side), loses expressiveness (only constructed combinations exist, so a rare topic-place-form intersection may have no heading at all), and loses maintenance (when the schema evolves, the enumerated headings must be re-cataloged rather than re-combined). The inference runs from "combination is eager" to each of these consequences at once — the designer reads them off the axis rather than discovering them case by case — and it predicts the mirror-image profile for the postcoordinated alternative.

A diagnostic move localizes a class of apparent coverage gaps. A search that finds no heading for an unusual combination is inferred not as an indexing oversight but as the structural signature of enumerating combinations in advance — the heading was never built because the space is enumerated, not constructed. The reasoning runs from a missing heading to the eager-composition design as cause, and it points directly to the interventionist lever: shift toward facets to move the combination cost back to the user, with the predicted effect that rare and novel intersections become expressible. This grounds a sorting move that reframes the open question "what heading does each resource need?" as the bounded one the design turns on: which combinations are worth building once and citing as whole strings (frequent, browsable, stable) versus which should be left for the user to assemble at query time (rare, novel, schema-volatile) — a single sort of the combination space along the eager/lazy line, with browsability, expressiveness, and maintenance all read off where a heading lands. A boundary move fixes scope: these inferences operate on classification-and-retrieval machinery — the fixed compositional grammar, the authority file of pre-built combinations, the single-string match — so they apply across the library-and-information-science family (LCSH, classified call numbers, enumerated subject codes), while the underlying eager-versus-lazy lesson, where it reaches further, belongs to the general precomputation-versus-deferral pattern rather than to compound subject headings specifically.

Knowledge Transfer¶

Within library and information science the precoordination design choice transfers as mechanism. The when-did-combination-happen inference, the linked trade-structure (browsability up, expressiveness and maintenance down), the missing-heading diagnostic, and the eager/lazy sorting lever carry intact across every classification-and-retrieval system that builds composite descriptors at indexing time. In subject cataloging, LCSH headings like "United States — History — Civil War, 1861–1865 — Personal narratives, Confederate" are the canonical case, with OCLC FAST and faceted thesauri as the postcoordinated alternative applied to the same descriptive territory. In classified shelving systems, Dewey and LC call numbers fuse class, region, period, and form into one string. In enumerated bibliographic taxonomies (pre-Internet abstracting services, hierarchical subject codes), composite codes are minted once and matched whole. A designer who learns to ask "which combinations are worth building once and citing as whole strings, and which should be left for the user to assemble?" carries that question and the facet-shift lever without translation across all of these, because they are one substrate: compositional descriptive vocabularies for retrieval.

Beyond that substrate the case is a clean (B): the precoordinated heading instantiates a general mechanism that genuinely recurs across domains, while its own compound-subject-heading machinery stays home. The portable structure is eager composition into a single canonical form versus lazy composition at use time — precomputation/materialization versus deferral — and that pattern really co-instantiates far beyond cataloging: eager-versus-lazy evaluation in programming languages, denormalized versus normalized storage and materialized versus computed views in databases, compiled versus interpreted execution, and prefabricated versus configurable products in manufacturing. (The entry's own Core Idea reaches for the database case directly: a precoordinated heading is to a postcoordinated facet set as a materialized denormalized join is to normalized tables combined at query time — and that is a real shared mechanism, because the eager/lazy trade is identical, not a mere resemblance.) So the cross-domain lesson — move combination cost to build time for cheap browsable reads, or to use time for expressiveness and easy schema evolution — should be carried by the general eager-versus-lazy / materialization parent, which is the right level to lift it. What stays home-bound is the library-specific cargo: the fixed compositional grammar of subject strings, the authority file of pre-built headings, the alphabetical card/shelf-list browsability, and the re-cataloging burden when the schema evolves. Invoking "a precoordinated heading" for, say, a cache or a materialized view borrows the eager/lazy shape but renames the components and drops the subject-vocabulary machinery; the honest move is to attribute the recurring trade to the precomputation-versus-deferral parent and reserve "precoordinated heading" for the LIS substrate where the grammar and authority file do real work (see Structural Core vs. Domain Accent).

Examples¶

Canonical¶

Consider how a cataloger builds the Library of Congress Subject Heading "United States — History — Civil War, 1861–1865 — Personal narratives, Confederate." The grammar fixes the positions: a main heading (the geographic/subject entity United States), a topical subdivision (History), a chronological subdivision (Civil War, 1861–1865), and a form subdivision (Personal narratives, Confederate). The cataloger assembles these once, before any patron searches, and records the whole string in the LCSH authority file, where the combination is sanctioned as valid. A reader seeking Confederate soldiers' memoirs then retrieves not by intersecting four separate facets but by matching this single canonical string, which files alphabetically on a shelf list beside its siblings. Had the reader wanted "Personal narratives, Union" instead, that would be a different, separately enumerated heading — it exists only if someone built it.

Mapped back: The full string is the composite label; the fixed slot order (entity, topic, period, form) is the fixed compositional grammar, and assembling it before any query is the eager combination at indexing time. Recording it against the sanctioned combinations is the authority file, retrieval by whole-string is the single-string match, and the Union variant existing only if built is the enumerated heading space.

Applied / In Practice¶

OCLC's FAST project (Faceted Application of Subject Terminology), developed from the late 1990s in cooperation with the Library of Congress, is a real-world response to precoordination's costs applied to the very same descriptive territory. LCSH's precoordinated strings, powerful for browsing card catalogs, proved hard to apply and maintain in online systems: catalogers needed deep training to construct valid strings, and the enumerated space struggled with novel combinations. FAST deconstructs LCSH's vocabulary into separate facets — topic, place, time period, form, and others — that can be assigned independently and combined by the retrieval system at query time. The payoff is the mirror-image trade: FAST is easier to apply and to evolve as the schema changes, and it expresses rare intersections that were never pre-built, at the cost of the direct alphabetical browsability a single fused string gives.

Mapped back: FAST's separate facets moved back to query-time assembly are the deliberate reversal of the eager combination at indexing time, relocating the combination cost to the user's system. Its easier maintenance and its capacity for un-pre-built intersections are the flip side of the enumerated heading space limitation, and its loss of shelf-list browsability is precisely the relocated combination cost read off the eager-versus-lazy axis in the other direction.

Structural Tensions¶

T1: Browsability versus expressiveness (the two ends one enumeration cannot both maximize). Precoordination's enumerated strings sort and shelve alphabetically with no retrieval-side composition — a real browsability payoff that follows directly from fusing dimensions at indexing time. But the same enumeration is what caps expressiveness: only combinations someone built exist, so a rare topic-place-form intersection may have no heading at all, and "Personal narratives, Union" is reachable only if a cataloger minted it. The gain and the loss are not two independent design knobs but one enumeration seen from two sides — every string that files neatly on the shelf is a string someone had to foresee and construct, and every intersection no one foresaw is simply absent. A vocabulary tuned for maximal browsability of frequent combinations is thereby tuned against expressing the long tail. Diagnostic: Is retrieval here dominated by browsing frequent, stable combinations, or by rare, novel intersections the authority file was never going to enumerate?

T2: Relocated cost versus eliminated cost (who pays for the compression, and whether they can). The compression precoordination offers the user — a multi-dimensional assembly problem collapsed to one act of string-matching — is genuine, but the combination cost does not vanish; it is moved off the retrieval side and front-loaded onto catalogers and schema designers who must construct and authority-control every composite string in advance. Cheap browsable reads are bought with expensive, expertise-heavy writes: FAST's own origin story is that LCSH strings proved hard to apply and maintain, demanding deep cataloger training. So the design is economical only where skilled indexing labor is available and reads outnumber writes; where cataloging capacity is the binding constraint, the front-loaded cost can dominate the retrieval-side savings it purchased. Diagnostic: Does this deployment have the expert indexing labor to pay the front-loaded combination cost, and do reads outnumber writes enough to amortize it?

T3: Missing heading as structural signature versus as genuine oversight (a diagnosis that can excuse a gap). The entry teaches that a search finding no heading for an unusual combination should be read not as an indexing oversight but as the structural signature of enumerating combinations in advance — a reframe that points at a design lever rather than a clerical fix. But it cuts both ways: the same frame can launder a real oversight as a principled exclusion, because the design offers no internal way to distinguish "this combination was deliberately not worth building" from "this frequent, stable, browsable combination should have been built and someone dropped it." Both present identically, as an absent string. Treating every gap as structural risks never fixing the genuine coverage failures; treating every gap as oversight abandons the insight that enumeration has principled limits. Diagnostic: Is this missing heading a rare, novel intersection the design rightly defers, or a frequent, stable combination whose absence is an actual cataloging failure?

T4: Canonical fixed grammar versus schema evolution (the fixity that enables matching resists change). The fixed compositional grammar — which element types occupy which positions — is what gives each heading its canonical, whole-matchable, alphabetically-filing form; without it the single-string match and the shelf-list browsability collapse. But that same fixity is precisely what makes the vocabulary expensive to evolve: when the descriptive schema changes, the enumerated headings must be re-cataloged rather than re-combined, because the combination is frozen into each string rather than computed on demand. The property that makes a heading a stable, citable object is the property that makes a corpus of them brittle under change. A postcoordinated facet set absorbs schema change by re-combining, paying instead in lost browsability. Diagnostic: Is the descriptive schema stable enough that the grammar's fixity is an asset, or evolving fast enough that the re-cataloging burden outweighs the browsability it secures?

T5: Lead-facet browsability versus cross-cutting slice (the single string privileges one dimension order). Fusing dimensions into one canonical string in a fixed order — entity, topic, period, form — makes the heading match whole and file alphabetically by its leading element, which is exactly the browsability win. But that same fixed order privileges the lead dimension and buries the trailing ones: a user who wants every "Personal narratives" regardless of place, or every heading with a given period across all topics, cannot slice by a trailing subdivision the way a postcoordinated facet intersection trivially would. Precoordination optimizes retrieval along the grammar's chosen axis and pays for it with cross-cutting queries that lead with a subordinate facet. The single-string match that eliminates intersection machinery also eliminates the intersection queries. Diagnostic: Do users here navigate by the heading's lead dimension, or do they need to slice by a trailing subdivision that the fixed string order makes inaccessible?

T6: Autonomy versus reduction (its own LIS construct or an instance of the eager/lazy parent that travels). "Precoordinated heading" is a genuine library-and-information-science construct with its own machinery — the fixed compositional grammar of subject strings, the authority file of sanctioned combinations, alphabetical card- and shelf-list browsability, the re-cataloging burden — and within LIS it travels intact across subject cataloging, classified call numbers, and enumerated bibliographic taxonomies. But beyond that substrate what recurs is not the heading but the general pattern it instantiates: eager composition into a canonical form versus lazy composition at use time — precomputation/materialization versus deferral — the same trade as eager-versus-lazy evaluation, materialized versus computed database views, and prefabricated versus configurable products. The cross-domain lesson belongs to that parent; the subject-vocabulary cargo stays home. Diagnostic: Resolve toward the precomputation-versus-deferral / eager-versus-lazy parent when asking what travels beyond cataloging, toward the named precoordinated heading when diagnosing a compositional descriptive vocabulary in situ.

Structural–Framed Character¶

Precoordinated heading sits on the framed side of the spectrum — best read as framed-leaning: a practice-constituted classification design choice, though one that rides a genuinely substrate-neutral structural trade. The one clearly structural-leaning mark is evaluative weight, which is low: the concept is explicitly "not strictly better or worse than postcoordination" — it names one end of an eager-versus-lazy axis and a trade-structure (browsability gained, expressiveness and schema-evolution lost), rendering a design analysis rather than a verdict. The other three of the home-pulling criteria point framed. It is human-practice-bound: a precoordinated heading is a decision catalogers and schema designers make, constituted by the practice of building descriptive vocabularies for retrieval — remove the cataloging practice and there is no heading, only a string. Its institutional origin is pronounced: the fixed compositional grammar of subject strings, the authority file of sanctioned combinations, and the card/shelf-list browsability convention are library-and-information-science furniture (LCSH the canonical case). And vocab_travels fails: compound subject headings, authority control, and re-cataloging burden are LIS-specific and do not float free. The strongly structural-pulling mark is import_vs_recognize: the underlying eager/lazy trade recurs across radically different substrates as genuine co-instances the entry insists are shared mechanism, not resemblance — materialized-versus-computed database views, eager-versus-lazy evaluation, compiled-versus-interpreted execution, prefabricated-versus-configurable products.

The portable structural skeleton is precomputation-versus-deferral — eager composition into a single canonical form versus lazy composition at use time — with its trade of cheap browsable reads against expressiveness and easy schema evolution. That skeleton is exactly what the precoordinated heading instantiates, not what makes "precoordinated heading" itself travel: the cross-domain reach belongs to the eager-versus-lazy / materialization parent (the right level to lift "move combination cost to build time or to use time"), while the compositional grammar of subject strings, the authority file, the alphabetical browsability, and the re-cataloging burden are the LIS accent that stays home. Its character: a practice-constituted, LCSH-institutional classification design construct whose portable spine is the substrate-neutral precomputation-versus-deferral trade, its compound-subject-heading grammar and authority-file machinery remaining bound to compositional descriptive vocabularies — framed-leaning, not a prime.

Structural Core vs. Domain Accent¶

This section decides why the precoordinated heading is a domain-specific abstraction and not a prime — marking where the portable eager-versus-lazy skeleton ends and the compound-subject-heading machinery begins.

What is skeletal (could lift toward a cross-domain prime). Strip the cataloging and a thin relational structure survives: multiple dimensions can be combined into one canonical form eagerly, at build time, so that use is a cheap whole-match, or left separate and combined lazily, at use time, so that use is expressive but must run composition machinery — and the combination cost is relocated, never eliminated, with browsability, expressiveness, and maintenance all reading off which end of that axis is chosen. The portable pieces are abstract — an eager/lazy composition axis, a relocated (not eliminated) combination cost, and a fixed trade-structure across the two ends. This is the precomputation-versus-deferral / materialization parent. The skeleton is genuinely substrate-portable, co-instantiating as eager-versus-lazy evaluation in programming languages, materialized-versus-computed database views, compiled-versus-interpreted execution, and prefabricated-versus-configurable products — genuine shared mechanism, not resemblance (the entry's own Core Idea reaches for the materialized-denormalized-join case directly). That portable core is what the precoordinated heading instantiates, not what makes it a precoordinated heading.

What is domain-bound. Almost everything that makes the construct this thing is library-and-information-science furniture and none of it survives extraction: the fixed compositional grammar of subject strings (which element types — topic, geographic, chronological, form — occupy which positions); the authority file of sanctioned pre-built combinations; the single-string match against alphabetically-filing card and shelf lists; the enumerated heading space (only constructed combinations exist); and the re-cataloging burden when the schema evolves. The worked vocabulary (LCSH's "United States — History — Civil War, 1861–1865 — Personal narratives, Confederate"), the instruments, and the empirical cases (FAST's faceted reversal) are the substance the field studies. The decisive test: invoking "a precoordinated heading" for a cache or a materialized view borrows the eager/lazy shape but renames every component and drops the subject-vocabulary machinery — what remains is the bare precomputation-versus-deferral parent, not a precoordinated heading.

Why this does not clear the prime bar. A prime is a relational structure whose vocabulary travels and whose cross-domain transfer is recognition of the same mechanism, not analogy. The precoordinated heading's transfer is bimodal. Within library and information science it travels as full mechanism — the when-did-combination-happen inference, the linked trade-structure (browsability up, expressiveness and maintenance down), the missing-heading diagnostic, and the facet-shift lever carry intact across subject cataloging, classified call numbers, and enumerated bibliographic taxonomies, because those are one substrate (compositional descriptive vocabularies for retrieval): genuine recognition of one design choice. Beyond that substrate the heading-as-named does not travel: databases, compilers, and manufacturing lines are co-instances of the parent eager/lazy trade, not of compound subject headings, and to call a materialized view "a precoordinated heading" would import the grammar-and-authority-file machinery by analogy. And when the bare structural lesson is needed cross-domain — move combination cost to build time for cheap browsable reads, or to use time for expressiveness and easy schema evolution — it is already carried, in more general form, by the precomputation-versus-deferral / eager-versus-lazy / materialization parent. The cross-domain reach belongs to that parent; "precoordinated heading," as named, carries the compositional grammar, authority file, alphabetical browsability, and re-cataloging machinery that stays home.

Relationships to Other Abstractions¶

Current abstraction Precoordinated Heading Domain-specific

Parents (4) — more general patterns this builds on

Precoordinated Heading is a decomposition of Classification Prime

A precoordinated heading is a catalog-specific design for assigning resources to governed composite categories under explicit construction rules.
Precoordinated Heading is a decomposition of Compositionality Prime

A heading's meaning is generated from controlled component meanings and their positions under a fixed compositional grammar.
Precoordinated Heading is a decomposition of Denormalization Prime

Precoordination stores a durable joined copy of separately governed dimensions, accepting synchronization burden for cheap whole-string access and browsing.
Precoordinated Heading is a decomposition of Precomputation and Materialization Prime

Removing subject-vocabulary machinery leaves eager combination before demand, a retained directly matchable artifact, and an update obligation.

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

Subject Heading String Domain-specific is a kind of Precoordinated Heading

Subject Heading String is the topical-main-heading species of Precoordinated Heading, adding ordered subdivisions and leading-substring browsing.

Hierarchy paths (4) — routes to 3 parentless roots

Precoordinated Heading → Classification

Show alternative paths (3)

Not to Be Confused With¶

Postcoordination. The opposite design choice, held in view throughout as the live alternative: keep the description dimensions as separate facets and combine them at query time, by the user's intersection, rather than pre-fusing them into one string. The precoordinated heading fuses eagerly at indexing time; postcoordination defers. They are the two ends of the same eager/lazy axis. Tell: are the dimensions combined once, before any search, into a whole-matched string (precoordination), or kept separate and intersected by the user at query time (postcoordination)?
Faceted classification. The concrete implementation of postcoordination — a vocabulary deconstructed into independently-assignable facets (topic, place, time, form) combined by the retrieval system (OCLC FAST is the case). It is the postcoordinated method applied to the same descriptive territory as precoordinated LCSH; naming it clarifies what the precoordinated heading is trading against. Tell: are subjects assigned as independent facets recombined at retrieval (faceted classification), or as pre-built canonical strings matched whole (precoordinated heading)?
Controlled vocabulary / authority control. The broader machinery of standardizing terms against an authority file — which the precoordinated heading uses but which also underlies postcoordinated and faceted systems. Authority control fixes which terms are valid; precoordination is the further choice to pre-combine them into composite strings. Part-versus-whole: a precoordinated heading is authority-controlled, but authority control does not imply precoordination. Tell: is the referent the standardization of allowable terms (controlled vocabulary), or the eager fusion of several into one canonical heading (precoordination)?
Classification notation / call number. A precoordinated string built for physical shelving — Dewey or LC call numbers fusing class, region, period, form into one browsable order. It is a sibling instance of eager combination within LIS, but keyed to shelf location rather than subject retrieval; both are precoordinated, but the notation orders books in space while the subject heading indexes topics. Tell: is the composite string primarily a shelf-location ordering device (call number), or a subject-access retrieval label (precoordinated subject heading)?
Tagging / folksonomy. User-supplied, uncontrolled keywords combined freely at query time — an extreme postcoordination with no authority file and no fixed grammar. The precoordinated heading is its opposite on both axes: eagerly combined and authority-controlled. Contrast case. Tell: are the descriptors free, user-minted tags intersected at search (folksonomy), or grammar-governed pre-built canonical strings (precoordinated heading)?
Precomputation-versus-deferral / eager-versus-lazy (parent pattern). The substrate-neutral trade the precoordinated heading instantiates — combine into a canonical form eagerly at build time (cheap browsable reads) versus lazily at use time (expressiveness, easy schema evolution). This is what travels to materialized views, eager/lazy evaluation, and prefabricated products; "precoordinated heading" is its LIS specialization. Treated more fully in the Knowledge Transfer and Structural Core vs. Domain Accent sections. Tell: strip the subject-string grammar and authority file and what remains — eager vs lazy composition with a relocated combination cost — is the parent, not the precoordinated heading.

Neighborhood in Abstraction Space¶

Precoordinated Heading sits in a crowded region of the domain-specific corpus (37^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Surface Form & Underlying Structure (23 abstractions)

Nearest neighbors

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