The Intellectual Foundation of Information Organization¶
Svenonius, E. (2000). The Intellectual Foundation of Information Organization. MIT Press.
Cited by¶
5 citations across 5 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Data Structure
- Libraries and archives. Card catalogs, shelf classifications, and finding aids are data structures over a corpus, privileging search-by-author, browse-by-subject, or trace-the-provenance differently.
This sourceTreats catalogs, classifications, and finding aids as arrangements over a corpus that privilege particular retrieval operations.
- Libraries and archives. Card catalogs, shelf classifications, and finding aids are data structures over a corpus, privileging search-by-author, browse-by-subject, or trace-the-provenance differently.
- Linearization-Meaning Mismatch
- And the multiple-index discipline from libraries — alphabetical-by-author, by-subject, and by-call-number are different consumer-need linearizations — transfers to API documentation, where by-call reference, by-task tutorial, and by-concept guide are all needed.
This sourceMultiple access points in library cataloging (author, title, subject, call number) as distinct user-need orderings of the same collection.
- And the multiple-index discipline from libraries — alphabetical-by-author, by-subject, and by-call-number are different consumer-need linearizations — transfers to API documentation, where by-call reference, by-task tutorial, and by-concept guide are all needed.
Domain-specific¶
- Aspect Qualifier
- Crucially, no descriptor named "aspirin-adverse-effects" exists in MeSH
This sourceThe standard account of pre- versus post-coordination, and of why a post-coordinate design lets a topic-plus-aspect claim live as a combination formed at indexing time instead of as a minted compound heading.
- Crucially, no descriptor named "aspirin-adverse-effects" exists in MeSH
- Precoordinated Heading
- 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
This sourcePrecoordinate versus postcoordinate subject languages, with postcoordination combining terms at the time a search is formulated.
Supported in partVerified against the source
- 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
- Topic Facet
- If yes, the dimension is not a clean facet and the decomposition will leak; if no, postcoordination dominates precoordination and the facet should be split off
This sourceSvenonius's Intellectual Foundation of Information Organization requires the categories of a classification to be mutually exclusive and treats precoordination versus postcoordination as a design choice.
Supported in partVerified against the work's full text
“complexity, automation, precoordination versus [postcoordination], and natural versus artificial syntax”
- If yes, the dimension is not a clean facet and the decomposition will leak; if no, postcoordination dominates precoordination and the facet should be split off
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 2 of 5 citations: 2 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:83d0651b24d0 · see in the full table