Toolbox / Infophilia Tools

Knowledge Structures Toolbox · 2026 Edition · iSchool Illinois

Toolbox: Standards, Systems & Tools for Organizing Information

A companion resource for the critical and open organization of information.

Toolbox is the companion to Core Readings: where Core Readings curates what to read and discuss, Toolbox catalogs what to consult and use — the descriptive and encoding standards, identifiers, classification and vocabulary systems, linked-data infrastructure, software, repository platforms, and library systems that do the actual work of organizing information.

It is a direct, openly licensed update to the 2001 Knowledge Structures Toolbox, rebuilt for a field that has moved from AACR2 to RDA, from MARC to BIBFRAME, from card catalogs to knowledge graphs — while keeping the historical layer visible rather than erasing it. Superseded systems stay on the page, dated and labeled, because knowing what a field replaced is part of knowing the field.

Scope: The Toolbox includes resources people use to organize, describe, and discover information, and the communities through which those resources are developed, maintained, and applied. Software, standards, services, vocabularies, and professional groups are included according to their practical contribution, not simply their format. Experimental resources may be included when they make an important development visible and their limitations are clearly stated.

Using this guide: to find a combination of resources for a piece of work, begin with Start with a task. Otherwise, each entry carries three pills — category, status, and access & licensing (explained under “How to read the labels”) — plus a brief annotation, cross-references, and a link where a stable one exists. Every entry has its own link (the address bar shows it when you follow a cross-reference). It is selective, not comprehensive, and does not duplicate entries already covered on Core Readings' Professional Resources section.

2001–2002 Knowledge Structures Toolbox IRLS 401/501, Organization of Information, University of Arizona. Preserved in dLIST.
mid-2000s MERIC Clearinghouse Metadata Education & Research Information Commons — proof-of-concept for a teaching commons.
2026– Toolbox The same commons-oriented premise, split into a readings register (Core Readings) and a tools register (this page).
Version 1.0 · living edition Last updated 18 October 2026 Maintainer Anita S. Coleman Canonical infophilia.codeberg.page
Category what kind of resource it is
Status Active · Emerging · Legacy · Historical
Access & licensing Open source · Open data / content · Free to access · Freeware · Paid / subscription · Source-available · Mixed · Restricted · Not applicable

How to read the labels

Each entry carries three small labels, displayed as rounded “pills.”

Category identifies the kind of resource, sometimes followed by a qualifier. The first term comes from a fixed set — Standard, Conceptual model, Vocabulary, Classification scheme, Authority file, Identifier, Software, Service, Organization, Project, Community resource, Teaching resource — and the qualifier after the dot is a short plain-language descriptor.

Status identifies the resource’s current role in practice. Active: currently maintained, supported, or established for operational use. Emerging: still developing toward routine use, or its adoption in the practice this Toolbox covers is limited or unsettled; it may already be operational, and the annotation states whether the reason is development, deployment, or adoption. A new release, version transition, or AI feature does not by itself make an established resource Emerging. Legacy: superseded or no longer substantially developed, but still used or materially present in operational workflows. Historical: retained principally for historical understanding rather than as a current operational option. Old, being replaced, and discontinued are not synonyms; a discontinuation is a fact stated in the annotation.

Access & licensing describes the resource named in the entry — not automatically its provider, documentation, underlying software, or associated services. Free access does not necessarily imply permission to modify or redistribute. Open source: software with a verified open-source license. Open data / content: data or content with stated reuse permissions. Free to access: reading or use is free; broader reuse rights are not implied. Freeware: free-to-use proprietary software. Paid / subscription: payment is required for the resource described. Source-available: the code can be inspected, but licensing restricts use or redistribution. Mixed: materially different free and paid components or access routes, which the annotation identifies. Restricted: use is limited to an eligible community, institution, or approved participants; the annotation names who is eligible. Not applicable: the entry describes an organization, program, concept, or unreleased tool for which an access label would mislead.

These labels are dated editorial assessments, not permanent properties; they reflect the editor’s assessment as of the “Last updated” date above. When a single set of labels would conceal an important difference between resources, those resources receive separate entries or an explicit qualification.

→

Start with a task

The sections below answer “What kinds of resources exist?” This index answers “Which combination do I need to accomplish this work?” Each route points into the existing entries. Routes suggest starting points and useful connections, not mandatory workflows. Some entries are alternatives; others work together. Read the short descriptions to decide which apply to your project. Bulleted routes are groups with no implied order, and some routes branch for different kinds of project. Tasks overlap, and an entry can belong to several.

Describe a resource

Record what a resource is: choose a vocabulary and content rules, then create the record in a format systems can exchange.

  1. DCMI Metadata Terms — start with a simple, cross-domain vocabulary
  2. RDA: Resource Description and Access — the content rules libraries use for what goes into a description
  3. MARC 21 — the exchange format most catalog records still travel in
  4. MODS — a schema-based alternative common in digital library systems
  5. Omeka Classic and Omeka S — practice: describe items in a working collection

Build or apply a vocabulary

Choose and apply controlled terms for subjects and other values, or build a vocabulary of your own.

  1. LCSH via id.loc.gov — apply an established subject vocabulary, with stable URIs
  2. FAST — a faceted, simpler way to apply the same headings
  3. NISO Z39.19 — the rules for constructing a controlled vocabulary
  4. SKOS — the standard for publishing a vocabulary as linked data
  5. Intentional Arrangement SKOS — practice: build a SKOS vocabulary in the browser

Reconcile names and identifiers

Match the names and identifiers in your records to shared authority and identity sources.

  1. LC Name Authority File (NAF) via id.loc.gov — the authority file most US library records point to
  2. VIAF — national authority files clustered into one identity hub
  3. ORCID — researcher identifiers that people register for themselves
  4. Wikidata — an open knowledge graph that links many identifier systems
  5. OpenRefine — practice: reconcile a spreadsheet of names against these sources

Define a local metadata profile

Decide how this project will use a standard: which properties, under what rules, with which values. See the table From vocabulary to validation in Section II.

  1. DCMI Metadata Terms — the vocabulary: what properties are available
  2. DCTAP — the profile: which properties this project uses, and under what rules
  3. SHACL — the rules made testable for linked data

Validate and transform records

Check records against the rules you set, then clean, convert, or map them.

  1. SHACL — how validation works for RDF data
  2. SHACL Playground — practice: run shapes against sample data and read the report
  3. schema.org Markup Validator and Google's Rich Results Test — check structured data on a web page
  4. OpenRefine — clean and normalize tabular data
  5. MarcEdit — batch-edit and convert MARC records
  6. MARC21 to LRM/RDA/RDF Mapping and Conversion Project — a worked mapping from MARC to LRM/RDA/RDF

Publish a collection

Put described items online where people and other systems can use them. Choose the branch that matches your project.

For a digital collection

  1. Omeka Classic and Omeka S — choose a publishing platform: a collections platform built on Dublin Core
  2. CollectionBuilder — or a lightweight static-site alternative
  3. DSpace — or an institutional repository for scholarly deposit
  4. IIIF — then investigate delivery options suited to that platform, such as interoperable image delivery
  5. OAI-PMH — and harvesting, so aggregators can collect your metadata

For a course reader

  1. Aletheia — assemble openly licensed readings and assignments into a reader
  2. Common Cartridge — export it as a package a learning platform can import
  3. Test the import in the learning platform your course actually uses; a package that opens cleanly in one platform may not in another

Preserve and transfer files

Package files with their metadata and checksums, verify the transfer, and keep copies over time. See the preservation table in Section X.

  1. PREMIS — what to record about an object's preservation history
  2. METS — how files and metadata fit together
  3. BagIt — how to package files so a transfer can be verified
  4. DART — practice: create and validate a bag
  5. CLOCKSS — who keeps copies for decades, and when they open

Provide discovery

Expose and search metadata so people find resources, from library interfaces to scholarly indexes and AI connectors.

  1. schema.org — make descriptions legible to search engines
  2. OAI-PMH — make metadata harvestable by aggregators
  3. VuFind — an open-source discovery interface over library records
  4. OpenAlex — scholarly discovery built on linked identifiers
  5. Yale Library AI Connector — AI-mediated discovery over curated library records

Optional, for scholarly publishing

  1. Eunomia's Labors — a service example showing how deposited identifiers and reference metadata support scholarly discovery

Document rights and provenance

Record what may be accessed, reused, or shared, whose authority informs that decision, and where the data came from. Grouped rather than sequenced: these apply alongside every other task.

Prepare a book's metadata for discovery and reuse

For an author or small press preparing a book so that libraries, search engines, and AI systems can find, identify, and reuse its metadata accurately. The theme is AI and linked data: identifiers and structured data travel further than a description alone. The Toolbox recommends no particular cataloging service. Disclosure: the maintainer is also an independent author and publisher.

  1. ISBN — identify each edition and format
  2. LCCN — a free Library of Congress control number, for eligible publishers
  3. CIP — cataloging before publication, for eligible publishers; independent authors may instead hire a cataloger
  4. ORCID — a persistent identifier the author registers and controls
  5. ISNI — an identifier for public identities that feeds VIAF and library authority files
  6. Cataloging Lab — community work on how authors and their names are represented in catalogs
  7. schema.org — describe the book and its author as structured data on the book's web page
  8. Wikidata — open items for the author and the work, linked to their identifiers
  9. Creative Commons — state reuse terms for anything you choose to license openly
I

Content & descriptive standards

The rules for what goes into a description, independent of the record format that carries it.

Standard · content rulesActiveMixed

RDA: Resource Description and Access · RDA Toolkit

Co-published by the American Library Association, the Canadian Federation of Library Associations, and CILIP (via Facet Publishing); day-to-day management sits with ALA Digital Reference. Replaced AACR2 as the standard for descriptive cataloging effective March 2013, built on the entity-relationship thinking of FRBR and now IFLA LRM. The Toolkit is a subscription service, with free options alongside it: a one-time 30-day free trial is available to anyone (rdatoolkit.org), and RDA-DACH and RDA-FR (links forthcoming) are free national adaptations for German- and French-speaking regions, hosted independently of the paid Toolkit by their respective national library consortia. RSC also runs its own YouTube channel and an annual Presentations page, including a current webinar series for African cataloguers (see the companion video entry in Core Readings).

Currently mid-transition: a "Countdown Clock" began 11 May 2026, retiring Original RDA as a live product on 12 May 2027 in favor of Official RDA. PDFs of every Original RDA page move immediately into Official RDA's own Instruction Archive; the web pages themselves are slated for eventual deposit in ALAIR, the ALA Institutional Repository — hosted at the University of Illinois Urbana-Champaign. This is a transition between versions of a delivery service, not a change in the standard’s current role in practice.

Teaching resourceActiveOpen data / content

Template RDA Teaching Slides · Elisa Sze, RDA Education and Orientation Officer (v. 15 November 2024)

RSC's own unbranded, adaptable slide deck for teaching RDA, licensed CC BY-SA 4.0 — reusable, not just a reference. Links back to specific Toolkit pages are embedded throughout, with citation numbers in the speaker notes. RSC updates it periodically when significant Toolkit changes warrant it, and continued to point to it as a current resource well into the Official RDA transition.

Conceptual modelActiveFree to access

IFLA Library Reference Model (LRM)

Consolidated the earlier FRBR, FRAD, and FRSAD models into a single conceptual framework (2017); RDA is built on it. See also Core Readings, Section II.

Conceptual model · ontologyActiveFree to access

LRMoo · object-oriented model of bibliographic information

The object-oriented counterpart to IFLA LRM: a formal ontology for bibliographic and museum information, designed as an extension of CIDOC CRM and aligned with LRM. Version 1.0 was fully approved in April 2024. IFLA’s Bibliographic Conceptual Models Review Group supports maintenance of LRM, FRBRoo, and PRESSoo, the related model for serials and other continuing resources. LRMoo is the model layer beneath projects that express library data as RDF, such as the MARC-to-LRM/RDA/RDF mapping in Section II.

Conceptual model · ontologyLegacyFree to access

FRBRoo · object-oriented version of FRBR, FRAD, and FRSAD

IFLA’s object-oriented recasting of the FRBR family (2017; version 2.4), now superseded by LRMoo, which succeeds and builds on it. Kept for context: LRMoo is understood in relation to it.

Standard · content rulesLegacyPaid / subscription

AACR2 · Anglo-American Cataloguing Rules, 2nd edition

The descriptive standard RDA replaced. Kept here, dated and labeled rather than erased, because a great many legacy catalog records still reflect AACR2 practice and hybrid records are common.

II

Encoding & exchange standards

How a description is structured and moved between systems — the working machinery of records, structural and preservation metadata, and domain-specific schemas.

Standard · encodingActiveFree to access

MARC 21

Still the most widely used record-exchange format in production catalogs, even as libraries transition toward BIBFRAME; the specification itself is freely published. Status here reflects its current role in practice, not its direction of travel.

See also: MODS.

Standard · linked dataEmergingFree to access

BIBFRAME · Bibliographic Framework Initiative

The Library of Congress's linked-data vocabulary for describing bibliographic resources, built to eventually succeed MARC. The entire LC catalog has now been converted at id.loc.gov; a Conversion 3.0 was announced in December 2025 and an update forum held in February 2026, showcasing production tools including the Marva editor and the Scriptshifter transliteration tool. Emerging here describes adoption, not readiness: BIBFRAME is in production use at the Library of Congress, but the field has not settled on it the way it still relies on MARC 21. See also knowledge graphs, Section VII.

ProjectEmergingMixed

MARC21 to LRM/RDA/RDF Mapping and Conversion Project · M2R / MARC2RDA

An independent, volunteer-led, open-source effort, begun in 2021 at the University of Washington Libraries, to map MARC21 bibliographic records to LRM/RDA/RDF and convert them with an XSLT transformation — a route from legacy records to the IFLA LRM and Official RDA that does not run through BIBFRAME. Phase I (concluded September 2025) covered single-expression manifestations and simple augmentation aggregates, and published mapping spreadsheets, transformation code, documentation, sample transformed records from the Library of Congress, the University of Washington Libraries, and the National Library of New Zealand, and an online conversion tool. Phase II extends the work to more complex aggregates and diachronic works. The project cautions that its output data and URIs are experimental, not persistent, and not ready for production. Co-led by Crystal E. Yragui and Cypress Payne (West Virginia University). The project’s documentation site is licensed CC BY-SA 4.0; the code license was not confirmed in the sources checked here, so confirm it in the repository before reuse.

Standard · metadataActiveFree to access

MODS · Metadata Object Description Schema

The Library of Congress's XML schema and guidelines for encoding a resource description. It can carry selected data from MARC 21 records and also supports original description, using language-based element names rather than MARC's numeric tags, which has made it a common descriptive layer in digital library systems; MODS records are often embedded in METS packages. Maintained by the MODS/MADS Editorial Committee with LC's Network Development and MARC Standards Office. Its companion for authority data is MADS (Section VI).

See also: MADS (Section VI), METS, MARC 21.

Vocabulary · metadataActiveFree to access

DCMI Metadata Terms · Dublin Core

The cross-domain vocabulary — the DCMI Metadata Terms, which extend the original fifteen-element Dublin Core set — still used and taught as one of the simplest on-ramps to structured description, and the schema Omeka is built around (Section IX).

See also: DCTAP.

Standard · metadataActiveFree to access

DCTAP · DC Tabular Application Profiles

A DCMI community specification for writing a metadata application profile as a table. Each row names a property and the rules for using it in one project: whether it is mandatory or repeatable, what kind of value it takes, and any constraint on those values. Only the propertyID column is required, and profiles are usually saved as CSV, so a profile can be drafted in any spreadsheet. DCTAP is the intermediate step between a general vocabulary such as DCMI Metadata Terms and the records a project creates. Supporting tools include dctap-python, which reads a profile and reports problems, and Tapir, a graphical editor; related tools generate SHACL shapes from a profile. A profile states rules; testing records against them is a separate step (see SHACL). The specification's license was not checked for this edition, so it is labeled Free to access. A sample profile for student projects is linked below.

See also: DCMI Metadata Terms, SHACL (Section VII), SHACL Playground (Section XIV).

Standard · metadataActiveFree to access

METS · Metadata Encoding & Transmission Standard

Structural metadata for digital library objects — how pages, files, and behaviors of a digital object relate to one another.

See also: MODS, BagIt.

Standard · metadataActiveFree to access

PREMIS · Preservation Metadata: Implementation Strategies

A widely used standard for documenting the preservation history and integrity of digital objects.

See also: BagIt, DART (Section X), CLOCKSS (Section X).

StandardActiveFree to access

BagIt · File Packaging Format (RFC 8493)

A set of file-layout conventions for storing and transferring digital content. A bag is a folder holding the payload files plus small text tag files, including a manifest that lists every payload file with its checksum, so a receiving system can verify that what arrived matches what was packaged. Developed by the Library of Congress and the California Digital Library; version 1.0 was published as RFC 8493 in October 2018. A packaging specification, not software: DART (Section X) creates and validates bags. The teaching question: what exactly travels with a digital object, and how do we check that the transferred files match what was packaged?

See also: DART (Section X), PREMIS, METS.

Standard · encodingActiveFree to access

TEI · Text Encoding Initiative

A widely used markup standard for representing humanities texts in machine-readable form; still very actively maintained.

Standard · encodingActiveFree to access

EAD · Encoded Archival Description

The archival finding-aid encoding standard. The Library of Congress presents EAD4 as the current version; EAD3 and the older EAD 2002 persist in existing finding aids and tools.

See also: ArchivesSpace (Section IX), AtoM (Section IX).

Standard · protocolActiveFree to access

IIIF · International Image Interoperability Framework

A widely adopted framework for interoperable delivery of digitized images and audiovisual material across institutions.

Standard · metadataActiveFree to access

PBCore

Metadata standard for public broadcasting and audiovisual archives.

Standard · e-learningLegacyFree to access

SCORM · Sharable Content Object Reference Model

Not primarily a metadata standard, despite often being filed as one — it's a content-packaging and runtime-communication specification (how an e-learning package is structured, and how it talks to the LMS via a JavaScript API), with a metadata layer folded in. Frozen since 2009 and still widely supported — many LMS platforms still import it — even though current guidance from the field treats it as legacy rather than the forward-looking choice.

See also: Common Cartridge.

Standard · e-learningActiveFree to access

xAPI (Experience API) / cmi5

xAPI (2013) tracks learning activity as "noun, verb, object" statements sent to a Learning Record Store, capturing activity SCORM can't see — offline, cross-device, outside the LMS entirely. cmi5 is a profile built on xAPI that adds back SCORM-style launch and completion structure. Some current guidance, including from the US Department of Defense, treats cmi5 as SCORM's intended successor for new development; SCORM's large existing content library is a main reason it has not been displaced outright. xAPI and cmi5 are related but not interchangeable: confirm which one a system actually supports.

See also: Common Cartridge.

Standard · e-learning packagingActiveMixed

Common Cartridge · 1EdTech

1EdTech's standard for packaging and exchanging digital learning materials and assessments between publishers, learning platforms, portals, and repositories, including links to LTI tools. A cartridge bundles content, activities, and assessments, and its learning objects can be tagged with topics, object types, and academic standards; version 1.4 adds accessibility and K-12 metadata. Mixed because version 1.3 is public while the 1.4 specification, implementation guide, validators, and certification materials are for members. These specifications address related but different problems: packaging and exchanging learning resources (Common Cartridge), packaging content and communicating with a learning platform at runtime (SCORM), and recording learning activity (xAPI and cmi5). They are not interchangeable. Aletheia (Section IX) is a reported implementation example: it exports Common Cartridge files, which is not evidence of certification or of tested compatibility beyond what its developer reports.

See also: SCORM, xAPI (Experience API) / cmi5, Aletheia (Section IX).

Standard · metadataLegacyMixed

IEEE LOM · Learning Object Metadata (IEEE 1484.12.1)

Present in the 2001 original under “Digital Learning Objects”; formally still alive (revised as recently as 2020, clearing IEEE's 10-year automatic-withdrawal rule), but its real ambition — a rich, nine-category schema meant to make learning objects discoverable and reusable across a networked ecosystem of repositories — never really arrived. All elements are optional, and most real records populate only a thin slice. Most often met today as the metadata layer folded into SCORM above. IEEE publishes the standard text, which is sold; free secondary descriptions exist.

Vocabulary · metadataActiveFree to access

schema.org

Cross-domain structured-data vocabulary consumed directly by search engines; used throughout this site's own JSON-LD. See also knowledge graphs and validation tools, Sections VII and XIV.

From vocabulary to validation

The Toolbox lists vocabularies and validators; the step between them is deciding how one project will use a standard. Four layers, each answering its own question:

LayerQuestion it answersOn this page
Vocabulary or schemaWhat descriptive properties are available?DCMI Metadata Terms, schema.org, MODS
Application profileWhich properties will this project use, and under what rules?DCTAP
Metadata recordWhat do we assert about this particular resource?Omeka, ArchivesSpace
ValidationDoes this record satisfy the specified rules?SHACL, SHACL Playground

A DCTAP profile takes a tabular form students can create in a spreadsheet: the rows identify properties and their rules, and the profile is saved as CSV. Start from the sample profile (prefix dct: = http://purl.org/dc/terms/). DCTAP states the rules; SHACL, or a tool that turns a profile into shapes, tests records against them.

III

Identifiers & identifier services

The standards and, distinctly, the registries and agencies that actually issue and resolve them.

Identifier · schemeActiveMixed

ISBN · International ISBN Agency and national agencies

Assignment runs through national agencies, and fees and terms vary by agency and country; in the US, ISBNs are assigned through Bowker for a fee. The scheme itself is not proprietary: the cost is a registration service — unlike most of the open identifiers below.

Identifier · schemeActiveMixed

ISSN · ISSN International Centre and national centers

Registered through national ISSN centers — in the US, through the Library of Congress — typically free to the depositing publisher. Terms vary by country, and access to the international registry’s database and services is separate from assignment.

Identifier · schemeActiveFree to access

LCCN · Library of Congress Control Number, via the Preassigned Control Number (PCN) Program

Missing from the 2001 original entirely; distinct from ISBN. PCN assigns only the number itself — no cataloging — which is what distinguishes it from CIP below. The service is free, but eligibility is restricted; see LC’s PCN pages for who may apply.

Service · catalogingActiveFree to access

CIP · Cataloging in Publication Program

One of the most consequential LC programs for daily cataloging practice. Eligible US publishers submit forthcoming titles through PrePub Book Link; an LC cataloger then does the actual work — full descriptive cataloging, subject headings, LC classification, and often DDC — before the book exists. The resulting CIP data block is printed on the book's copyright page and distributed electronically to libraries and vendors in advance of publication. For a cataloger, a CIP block is frequently the starting point for a full record rather than something built from scratch: LC's own cataloging labor here becomes reusable by every other library that acquires the book. Distinct from PCN above, which assigns only the control number with no cataloging attached; eligibility differs between the two programs, so check LC’s current CIP and PCN eligibility pages before assuming either is closed to a given publisher. Program availability depends on funding: PrePub Book Link submissions were reported suspended during the October–November 2025 federal shutdown. Check LC’s program page for current status.

Identifier · schemeActiveMixed

DOI · registered through Crossref (scholarly literature) or DataCite (datasets and research objects)

"DOI" names the identifier scheme; Crossref and DataCite are two of several registration agencies that actually register them, and it's the agency, not the DOI Foundation abstractly, that a depositing organization deals with. Resolving a DOI is free, but registering one usually costs the depositing organization; fees vary by agency.

See also: Eunomia's Labors.

Service · scholarly metadataActiveFree to access

Eunomia's Labors · Crossref deposits for rhetoric and composition journals

A free service, run by Justin Lewis (Olympic College), that helps small rhetoric and composition journals register DOIs with Crossref and deposit the reference lists that go with them. It keeps two jobs distinct: registering a DOI identifies an article, while depositing its reference list records what the article cites, which is what makes citation networks possible downstream. For each journal, Lewis builds a scraper for the archive, extracts reference lists, matches them against existing DOIs, audits the results by hand, and produces a validated deposit file. The service itself carries no charge; the journal pays Crossref for membership and DOI registration and keeps control of its own DOI prefix and credentials. Lewis has no affiliation or partnership with Crossref. Its site reported six journals and about 31,000 deposited references as of September 2026. A sister site to Pinakes, whose citation data depends on exactly these deposits.

See also: DOI, Pinakes (Section XII).

Identifier · registryActiveMixed

ORCID

Open, persistent researcher identifier; the registry itself, distinct from ORCID-the-concept. Central to this site's own entity-resolution practice. Individual registration is free; terms for institutional membership and API use differ.

Identifier · registryActiveMixed

ISNI · International Standard Name Identifier

Persistent identifier for public identities — people and organizations — feeding into VIAF and library authority files (Section VI). Public lookup is separate from assignment: terms and fees for assignment vary, so check with the ISNI agency.

Identifier · schemeActiveFree to access

ARK · Archival Resource Key

Persistent identifier scheme widely used by libraries and archives for digital objects, independent of any single resolver. The scheme is free to use; hosting a resolver and managing the identifiers has its own costs.

IdentifierActivePaid / subscription

Proprietary author identifiers · Scopus Author ID, Web of Science ResearcherID

Distinct from ORCID/ISNI above: these are controlled by the vendors that issue them, so their terms and portability differ from ORCID and ISNI, even though they're commonly encountered alongside the open identifiers in the same workflows.

IV

Classification tools

Shelf and notation schemes, and the access tools that make them usable in practice. A working distinction for this section: WebDewey and Classification Web support human classification decisions, while the AI features in Section VIII propose metadata for a human to evaluate.

Classification schemeActiveMixed

Library of Congress Classification (LCC) · Classification Web

The classification scheme is published by the Library of Congress; the outline is publicly browsable, while full working access to Classification Web is a paid subscription. The free LC Classification Outline gives the main classes and subdivisions, a stable place to learn the logic of LCC before using the schedules.

Classification schemeActiveMixed

Dewey Decimal Classification (DDC) · WebDewey

DDC is a licensed scheme, and WebDewey is OCLC's subscription tool for full access; DDC itself has also been converted to linked data as part of OCLC's WorldCat Entities work (Section VII). OCLC also publishes DDC Summaries, an overview of the ten main classes and their divisions, a lighter way to see the structure without a subscription; use is subject to OCLC's terms.

Classification schemeActiveMixed

Universal Decimal Classification (UDC)

Maintained by the UDC Consortium. The UDC Summary is free to browse online; the full scheme (the Master Reference File) is licensed, so the summary should not be taken as access to the whole classification.

Classification schemeActiveFree to access

NLM Classification

Still actively maintained by the National Library of Medicine, updated in winter and summer editions each year (check the site for the current edition).

Classification schemeHistoricalMixed

Colon Classification · S. R. Ranganathan

The first fully faceted, analytico-synthetic scheme, developed by Ranganathan between 1924 and 1928 and first published in 1933; its seventh edition (1987) appeared posthumously. Built on five fundamental categories — personality, matter, energy, space, and time (PMEST) — combined by a citation order. Little used for shelving today and not being adopted by new libraries, but still taught, and the clearest way to see facet analysis and a faceted approach set beside the enumerative LCC and DDC. See also UDC above, and Core Readings. Retained here principally for teaching rather than as a current operational option. The scheme itself was published in print editions and its current access terms were not verified for this edition; the linked ISKO Encyclopedia article is free to read.

See also: Madras Library Association (MALA) (Professional organizations), Sarada Ranganathan Endowment for Library Science (SRELS) (Professional organizations).

Vocabulary · subject headingsActiveMixed

BISAC Subject Headings · Book Industry Study Group (BISG)

The subject categorization used across publishing and bookselling, assigned by publishers so that retailers can place a book on the right shelf or page. A useful contrast with library-controlled vocabularies: who assigns the subject, for whom, and for what purpose. BISG lets anyone browse the full list free of charge (2025 edition); a paid license is needed to download the complete list for use in business systems, and redistribution without permission is not allowed.

Service · web toolHistoricalNot applicable

OCLC Classify · experimental classification service

Developed in 2008 as an experimental service that suggested Dewey and LC classification numbers and related subject headings drawn from WorldCat records. OCLC discontinued its web interface and API on 31 January 2024, citing aging infrastructure, so it is no longer something to assign. It is kept here, dated and labeled, because it appears in a great deal of cataloging teaching material. OCLC points subscribers to WorldShare Record Manager and the WorldCat Metadata API, which can return the most popular LC and Dewey numbers for an OCLC number.

V

Vocabulary control & subject access

Controlled vocabularies, thesauri, and the standards for building them.

Vocabulary · subject headingsActiveFree to access

LCSH via id.loc.gov

Library of Congress Subject Headings, now published as linked data with stable URIs.

Vocabulary · subject headingsActiveOpen data / content

FAST · Faceted Application of Subject Terminology

OCLC and LC's simplified, faceted derivative of LCSH, built for low-cost application at web scale by non-specialist staff; released under an open data license.

Vocabulary · subject headingsActivePaid / subscription

Sears List of Subject Headings

The children's- and school-library-oriented counterpart to LCSH, regularly revised as a licensed publication.

Vocabulary · thesaurusActiveFree to access

Thesaurus for Graphic Materials (TGM)

Library of Congress vocabulary for indexing pictorial and graphic materials.

Vocabulary · thesaurusActiveFree to access

Art & Architecture Thesaurus (AAT) · Getty Vocabularies

Now published as Linked Open Data alongside Getty's other vocabularies (ULAN, TGN).

Vocabulary · thesaurusActiveFree to access

MeSH · Medical Subject Headings

The National Library of Medicine's controlled vocabulary for biomedical literature.

Standard · vocabulary constructionActiveFree to access

NISO Z39.19 · Guidelines for the Construction, Format, and Management of Monolingual Controlled Vocabularies

The US baseline for constructing monolingual thesauri. The edition linked here is Z39.19-2005 (R2010), so check NISO for the current status. See also SKOS, Section VII, the encoding such vocabularies are now typically published in.

Standard · vocabulary constructionActivePaid / subscription

ISO 25964 · thesauri and interoperability with other vocabularies

The international standard for thesauri, covering interoperability between vocabularies; it complements and in part succeeds Z39.19 above. ISO standards documents are typically sold (see ISO, Section XIV), unlike the NISO standard above.

Software · metadata toolEmergingSource-available

Intentional Arrangement SKOS · Jessica Talisman (2026), v0.17.3

A browser-based editor for building SKOS controlled vocabularies, taxonomies and thesauri, with SKOS-XL labels, ISO 25964 relationships, Dublin Core metadata, qSKOS validation and SPARQL querying. Imports and exports Turtle, RDF/XML, JSON-LD, CSV and Excel. Runs entirely in the browser, so vocabularies stay local unless you choose to publish them. Licensing is size-based and source-available, not OSI-approved open source: free to eligible small organizations (fewer than 75 employees, counting affiliated entities), with a separate written enterprise license required above that, which will apply to most university libraries. Taxonomies you create remain your own. Emerging here describes both development and adoption: the tool is new (2026; v0.17.3 at the time of writing), and adoption in cataloging practice is not yet documented on this page. A companion to Talisman’s Ontology Pipeline (see Core Readings).

Vocabulary · place namesActiveFree to access

GeoNames

An open geographical database of place names and coordinates, widely used for linking place names in metadata. Data is freely available; check its current license terms before reuse.

Vocabulary · place namesActiveFree to access

GEOnet Names Server · U.S. National Geospatial-Intelligence Agency

The NGA’s database of foreign place names, the 2001-era source for such names. It is a distinct resource from GeoNames.org; confirm its current availability and update schedule with the NGA before relying on it.

See also: Homosaurus and Indigenous classification systems, both deliberately placed in Section XV (Critical & Reparative Cataloging) rather than duplicated here.

VI

Authority control & linked-data identity

Establishing consistent access points for names, and the shift from siloed authority files to shared identity infrastructure.

Authority fileActiveFree to access

LC Name Authority File (NAF) via id.loc.gov

Now published as linked data with stable URIs, replacing the vendor-specific authority lookups (e.g. the defunct DRA LC Authority Search) that the 2001 page pointed to.

See also: MADS.

Authority fileActiveFree to access

VIAF · Virtual International Authority File

Aggregates national authority files into a single linked-data identity hub; didn't exist in 2001.

Authority fileActiveFree to access

SNAC · Social Networks and Archival Contexts

A free, online resource for discovering primary source documents — photographs, letters, sound recordings — held by archives, libraries, and museums, and for tracing connections among the people, families, and organizations behind them across time and place. SNAC records are authority records, linked to one another by context and to other authority records, finding aids, and resources elsewhere. Hosted by the University of Virginia Library and the University of Maryland's IndigenizeSNAC, with support from the Andrew W. Mellon Foundation, the Institute of Museum and Library Services, and the National Endowment for the Humanities. Its SNACSchool offers training in creating, editing, and merging records, and recordings of past sessions are posted publicly.

Standard · metadataActiveFree to access

MADS · Metadata Authority Description Schema

MODS's companion: an XML schema for describing authoritative entities, namely agents such as people and organizations, events such as conferences, and terms such as topics, places, and genres. Most MADS elements have equivalents in the MARC 21 Authority Format, which makes it a bridge between the encoding standards in Section II and the authority files in this section. Maintained by the MODS/MADS Editorial Committee with the Library of Congress.

See also: MODS (Section II), LC Name Authority File (NAF) via id.loc.gov.

OrganizationActiveNot applicable

Program for Cooperative Cataloging (PCC) · NACO, SACO, BIBCO, CONSER

The actual participation structure behind authority-record contribution, absent from the 2001 page entirely. Distinct in angle from Core Readings' PCC Task Group on AI/ML link — that one is a report to read, this is the governance program itself. PCC’s documentation is public; contributing through NACO, SACO, BIBCO, or CONSER requires institutional participation.

See also: ISNI and ORCID (Section III) and Wikidata as an identity hub (Section VII) — all doing adjacent authority-adjacent work, not duplicated here.

VII

Semantic web & knowledge graphs

The technology stack beneath linked data, and knowledge graphs as its most consequential current application, plus the standard for testing whether linked data meets stated requirements.

Standard · linked dataActiveFree to access

RDF / RDFS / OWL

The W3C stack underlying every linked-data vocabulary on this page — BIBFRAME, schema.org, SKOS vocabularies, and the identity graphs below.

Standard · linked dataActiveFree to access

SKOS · Simple Knowledge Organization System

The W3C standard now used to publish thesauri and controlled vocabularies as linked data. See also Section V.

Standard · linked dataActiveFree to access

SHACL · Shapes Constraint Language

The W3C standard for checking whether RDF data meets stated requirements. A validator takes a data graph and a shapes graph, the rules written as node and property shapes, and produces a validation report, itself an RDF graph, listing each result. It supplies the missing link between publishing linked data and testing it. SHACL became a W3C Recommendation in 2017, and a SHACL 1.2 revision is in draft. To run validation rather than read about it, use the SHACL Playground (Section XIV).

See also: DCTAP (Section II), SHACL Playground (Section XIV), RDF / RDFS / OWL.

Service · knowledge baseActiveOpen data / content

Wikidata

The leading open knowledge graph; its data is CC0. Wikidata was recognized as a Digital Public Good in October 2025. Zenodo’s community pages — including the ALISE ART and Infophilia Research communities — sit adjacent to this same linked-data ecosystem.

See also — knowledge graphs. Google’s Knowledge Graph (2012) popularized the term, and Wikidata is the leading open example. OCLC’s WorldCat Entities is the concrete, current library-sector case: past 150 million entities, adding URIs for Works, Persons, Places, Organizations, Concepts, and Events directly into WorldCat MARC records as $1 links, with DDC itself converted into linked-data “concept” entities as of late 2024. help.oclc.org/WorldCat_Entities

See also: Scholia (Section XII), OpenAlex (Section XII), LINCS.

SoftwareActiveOpen source

Wikibase

The open-source software underlying Wikidata, which institutions can also run on their own to build a separate linked-data knowledge base. Distinct from Wikidata itself: the software and the data have different openness arrangements.

ProjectActiveOpen data / content

LINCS · Linked Infrastructure for Networked Cultural Scholarship

A Canadian infrastructure project that converts, connects, enhances, and publishes cultural research as linked open data for the humanities. It runs in the Digital Research Alliance of Canada cloud, with storage and preservation through University of Victoria Libraries and the Borealis Dataverse. CIDOC CRM is its core ontology, with extensions including FRBRoo and CRMdig; published data is queryable through SPARQL endpoints, and its tools include ResearchSpace. Its data management plan commits published data to the FAIR principles and, for Indigenous and Traditional Knowledges, to the CARE Principles; final linked data is typically released under CC BY 4.0, with an exemption from open sharing available for reasons such as data sovereignty or community rights, and its code is open source. One example dataset, Historical Canadians, created by Jim Clifford, Susan Brown, and others, draws on the Dictionary of Canadian Biography with Wikidata and models families, occupations, and residences; its team chose not to carry over nationality and ethnicity designations because decolonized vocabularies for First Nations, Inuit, and Métis people were lacking. The far end of the spectrum from a personal research graph: formal ontologies, persistent identifiers, and institutional infrastructure. Checked 18 October 2026.

See also: Wikidata, FRBRoo (Section I), SPARQL (Section XIII), Local Contexts (Section XV).

VocabularyLegacyFree to access

WordNet

Princeton's electronic lexical database; Princeton states that it is no longer developed, though the database and tools remain freely available to download. Its role has also diminished relative to newer NLP resources since 2001.

VIII

Cataloging, metadata management & quality tools

Software for the actual, daily work of batch-editing, reconciling, and cataloging records, now including vendor features that use AI to suggest subjects and classification. For those, the vendor’s documentation is the primary source for how the workflow and its safeguards are described; it is not evidence of how accurate or unbiased the output is. A closing subsection widens the view to metadata management, quality, and provenance for organizational data.

Software · metadata toolActiveFreeware

MarcEdit

Terry Reese's free, widely used MARC batch-editing tool. Freeware, not open source: the developer states that MarcEdit is not open source; includes linked-data tooling (MARCNext) resolving to VIAF, id.loc.gov, and FAST.

Software · metadata toolActiveOpen source

OpenRefine

General-purpose tool for cleaning and reconciling messy tabular and non-MARC data against external vocabularies; more flexible than MarcEdit but with a steeper learning curve, and often used alongside it.

See also: OpenMetadata.

Software · metadata toolActivePaid / subscription

OCLC Connexion · cataloging client

OCLC’s cataloging client, distinct from the web-based WorldShare Record Manager below and from WorldShare Management Services, the full LSP (Section XI). Its AI Enrichment macro is listed below.

Software · metadata toolActivePaid / subscription

WorldShare Record Manager

OCLC’s web-based cataloging interface, a different tool from the Connexion client and from WorldShare Management Services. OCLC points former Classify users to Record Manager and the WorldCat Metadata API (see OCLC Classify, Section IV).

Software · AI featureActivePaid / subscription

OCLC AI Enrichment macro · Connexion client

A macro for the Connexion client (OCLCAIEnrichment in Macro Manager) that proposes Dewey Decimal Classification numbers, Library of Congress Classification numbers, and Library of Congress Subject Headings for an open record or workform — up to three classification and five subject suggestions. OCLC states that the suggestions are based on existing WorldCat data; the cataloger checks which to add and may edit the fields afterward. A title is required, and a name and summary give the best results. OCLC's help page dates from October 2025 and was revised in December 2025.

Software · AI featureEmergingPaid / subscription

AI Metadata Assistant · Alma Metadata Editor, Ex Libris (Clarivate)

A generative-AI feature that proposes MARC 21 metadata — subjects, summary notes, content notes, and other fields — to create a new bibliographic record or enrich a brief one, working from a title plus optional author, ISBN, notes, or uploaded images and documents. Ex Libris says the suggestions are for review by a cataloger, appear as unsaved drafts marked “AI Generated” or “AI Enriched,” and may reflect “limitations, inaccuracies, or biases.” Phase I covers English-language MARC 21 records for books and LC authorities. The feature is off by default; an institution's administrators enable it and assign catalogers a dedicated AI Assisted Cataloging role. Ex Libris states that submitted data is used only for processing, not for training. Emerging here describes development stage: the documentation calls this Phase I, with more languages, formats, and vocabularies planned. Documentation last modified May 2026.

Software · AI featureActivePaid / subscription

Digital Metadata Assistant / Metadata Enrichment · Alma Specto, Ex Libris (Clarivate)

An AI feature for digital collections: it analyzes a digital resource's content together with its existing metadata and proposes bibliographic fields, including LCSH subject headings (checked against GND for German) and the MARC 21 347 field for digital file characteristics. Generated fields appear in a distinct color and the title becomes a Working Copy; a provenance note records that AI helped create part of the record. The documentation tells catalogers to check warnings and errors before approving, and to approve or edit at the title level. Documentation page last updated October 2026.

Software · metadata toolActivePaid / subscription

Normalization rules · Alma Metadata Editor, Ex Libris (Clarivate)

Rules, written in Drools or XSL, that edit or delete fields in bibliographic metadata, conditionally if needed. They run when a record is saved, from the “Enhance the record” menu, on records brought in through import profiles or external searches, and in batch on sets of records. Ex Libris documents them as explicit, programmed rules, not AI — a useful contrast with the AI Metadata Assistant above. Part of Alma, so access depends on an institution’s Alma subscription. Alma's training materials also cover Browse Shelf Listing in the Metadata Editor, alongside searching external resources and browsing headings.

Software · metadata toolEmergingNot applicable

ErgoCat · Casey Mullin, Cataloger in the Loop

A sabbatical-stage cataloging interface built from scratch to explore what generative AI and current tooling could do for metadata work, starting with music formats. Chronicled openly, module by module, in a free newsletter. The newsletter is free to read, but the software is not yet distributed, so no access terms for the tool itself are established — not yet a finished, installable tool the way MarcEdit is, which is exactly why it earns the Emerging status rather than a stretched Active. The clearest current example of the case this pill exists for.

Metadata management, quality & provenance

A library catalog helps people identify and discover resources. An organizational data catalog also helps people discover data assets, but adds questions such as who is responsible for them, how they were produced, what quality checks apply, and what other systems depend on them.

Software · metadata managementActiveOpen source

OpenMetadata

An Apache-2.0-licensed platform for discovering, documenting, and governing organizational data assets. It connects technical metadata with glossaries, classifications, ownership, data-quality information, and lineage, helping users understand what data exists, what it means, where it came from, and what depends on it. A useful comparison with library catalogs and authority systems: its primary focus is organizational data infrastructure rather than bibliographic collections, and lineage is provenance for data assets. Community documentation, a Slack community, and contribution guides are linked from its repository; commercial managed services are offered separately through Collate. Not to be confused with Egeria's "Open Metadata and Governance." An example from organizational data management that extends the Toolbox's library-centered view of metadata.

See also: OpenRefine, PREMIS (Section II).

IX

Collection display & social cataloging tools

Tools that describe and expose collections to the public — through formal schema on one hand, crowdsourced tagging on the other — followed by the environments archivists use to create and manage archival description.

Software · digital collectionsActiveOpen source

Omeka Classic and Omeka S

Dublin Core is native to Omeka’s schema, making Omeka one of the better hands-on ways to teach structured description. Omeka Classic and Omeka S are free, open-source software (GPL-3.0) that an institution installs and hosts itself.

Service · hostingActiveMixed

Omeka.net

The hosted version of Omeka, as distinct from the installable software above. It still has a free plan, but that plan is scoped to a single site with limited themes and plugins; paid plans differ. Verify current terms before building a syllabus around it.

Service · catalogingActiveMixed

LibraryThing

A social cataloging site. It teaches the opposite lesson from Omeka: uncontrolled, crowdsourced tagging as a counterpoint to controlled vocabulary. Free and paid membership options exist; check current terms. See also LCSH/FAST, Section V, for the controlled-vocabulary contrast.

Service · catalogActivePaid / subscription

LibraryThing for Libraries (LTFL)

A separate, library-facing product that adds enhancements to a library’s own catalog. LTFL continues shipping OPAC enhancements (tag clouds, “similar books,” ratings and reviews) into 2026.

Service · catalogActivePaid / subscription

TinyCat

The companion small-library OPAC product from the LibraryThing family. Distinct from LibraryThing, which is the social cataloging site, and from LTFL, which enhances an existing catalog.

Software · digital collectionsActivePaid / subscription

CONTENTdm

OCLC's institutional-grade digital collections platform — the heavier-weight sibling to Omeka.

Software · repositoryActiveOpen source

Islandora

Drupal-based digital repository framework that works with a Fedora repository backend (Section X), common in academic and research library digital collections. Architecture and components differ between Islandora versions, so check the version in use.

Software · digital collectionsActiveOpen source

CollectionBuilder

Newer, lightweight, static-site-generator-based digital collections tool gaining real traction in LIS teaching specifically because it is open source and needs no application server (hosting, building, and maintenance still have their own costs) — a possible fallback if Omeka.net's free tier keeps shrinking.

Course readers & resource assembly

Organizing work that selects resources, arranges them into a reader or course sequence, and exports the result for teaching. Not an archival platform and not a direct equivalent to Omeka: the unit of organization is a course, not a collection.

Software · course-reader builderEmergingOpen source

Aletheia · open course readers for writing classes

A web tool by Justin Lewis for assembling open-access course readers and assignment sets for rhetoric, composition, and writing-studies classes. An instructor chooses a course focus, starts from a sample course or a blank one, fits it to a term of five to sixteen weeks, and selects from an index of about 2,000 openly licensed readings and 500 assignments; an outcomes tool checks coverage against documents such as the WPA Outcomes Statement, using word-stem matching rather than an AI model. The result exports as a reader (HTML or PDF), a print PDF, a Common Cartridge package, a calendar file, and a .docx syllabus, and a program mode produces a zero-textbook-cost report. The organizing work is selection, arrangement, and packaging, not description. Emerging describes development: the repository describes the project as in early development (October 2026). The code is MIT-licensed and the catalog records are CC BY 4.0, while the works it points to keep their own licenses (checked 18 October 2026). The developer reports that the print PDF is not tagged for accessibility, that the Common Cartridge export has been tested only on Canvas, and that generated courses are a skeleton for instructors to complete.

See also: Common Cartridge (Section II), Pinakes (Section XII).

Archival description environments

EAD (Section II) and SNAC (Section VI) describe how archival descriptions are encoded and connected; these environments are where archivists actually create and manage them. Three distinctions to keep in view: the descriptive work is not identical to the encoding, the software interface is not identical to the underlying standard, and exporting valid XML does not by itself settle the quality of the description.

Software · archival descriptionActiveOpen source

ArchivesSpace

An open-source, browser-based archives information management system that supports accessioning, arrangement and description, agent and subject records, rights, and reference work. Its underlying descriptive standard is DACS, and it imports and exports EAD, EAC-CPF, MARCXML, METS, MODS, and Dublin Core. Yale Library's implementation documentation, linked below, notes that resource descriptions are based on DACS and can be serialized as EAD, so archivists create descriptions without writing XML directly. Lyrasis is its organizational home, and it is developed under a community membership model. It is not a digital asset management system.

See also: EAD (Section II), SNAC (Section VI), AtoM.

Software · archival descriptionActiveOpen source

AtoM · Access to Memory

A web-based, open-source application for standards-based archival description and public access in a multilingual, multi-repository environment. First commissioned by the International Council on Archives, it is built around ICA standards (ISAD(G), ISAAR(CPF), ISDIAH) and imports and exports EAD. Developed and maintained by Artefactual Systems under the AGPLv3 license, with paid hosting and support offered separately. A useful contrast with ArchivesSpace: AtoM leads with public description and access across institutions and languages, ArchivesSpace with the archivist's internal workflow.

See also: ArchivesSpace, EAD (Section II).

X

Repository platforms

Software for scholarly deposit, open-access mandates, and preservation — interoperable via OAI-PMH and SWORD, distinct in job from the display tools above — followed by the tools and services that package files for transfer and keep copies over time.

Software · repositoryActiveOpen source

DSpace

DSpace 7 introduced a new architecture and interface; the project’s own site now discusses DSpace 10 (news posts dated September 2026). Check dspace.org for current release and migration details before planning around any version.

Software · repositoryActiveOpen source

EPrints

An open-source institutional repository platform from EPrints Services at the University of Southampton, in use for more than two decades. Check eprints.org for the current stable release.

Software · repositoryActiveOpen source

Fedora

The third leg of the classic DSpace/EPrints/Fedora institutional-repository triad; the backend Islandora (Section IX) is built on top of.

Software · repositoryActiveOpen source

Invenio

CERN-built repository framework; InvenioRDM, an application built on it, is the software Zenodo runs on.

Software · repositoryActiveOpen source

Dataverse

Harvard-originated platform built specifically for research-data deposit, distinct from the document-oriented focus of the platforms above.

Preservation transfer & services

PREMIS and METS (Section II) say what to record and how to wrap it; the repository platforms above say where it lives. This subsection covers how files travel and who keeps copies over time.

SoftwareActiveOpen source

DART · Digital Archivist's Resource Tool

An open-source desktop application from the Academic Preservation Trust (APTrust) for creating BagIt bags that conform to a BagIt profile, validating them, and uploading them to S3-compatible or SFTP storage, with a point-and-click profile editor and repeatable workflows. DART 3 builds jobs in its graphical interface and runs them through a companion command-line tool, DART Runner. Chosen here over Bagger, whose repository states that the Library of Congress is reviewing next steps for its future.

See also: BagIt (Section II).

ServiceActiveMixed

CLOCKSS · Controlled LOCKSS archive

A dark archive for web-published scholarly content, governed by participating publishers and libraries and built on LOCKSS (Lots of Copies Keep Stuff Safe) technology from Stanford, with copies held at twelve archive nodes at libraries around the world. Content stays dark until a trigger event, such as a journal disappearing from the web, when the CLOCKSS Board can release it for free public access. Participation is funded by publisher and library fees while triggered content is free to everyone, hence Mixed. The Center for Research Libraries certified it as a trustworthy digital repository in 2014. It answers a different question from BagIt and PREMIS: who holds copies for decades, and under what conditions do they open?

See also: BagIt (Section II), PREMIS (Section II).

What travels, and who keeps it

LayerExampleQuestion
What to recordPREMISWhat do we need to know about this object’s history?
How to wrap itMETSHow do the files and metadata fit together?
How to move itBagIt + DARTDid what arrived match what was sent?
Where it livesRepository platforms aboveWho manages it day to day?
Who keeps copiesCLOCKSSWho holds copies for decades, and under what conditions do they open?
XI

Library automation systems: ILS → LSP

What the 2001 page called "Bibliographic Utilities" and "Specific Cataloging Services," modernized — the production systems libraries actually run their catalogs on, and the one continuous lineage connecting the two eras.

Software · library systemHistoricalPaid / subscription

NOTIS & Dynix · the Ameritech lineage

NOTIS was Northwestern's mainframe system; its demise was structural, not competitive — it ran on IBM mainframes that became obsolete as smaller servers took over. Dynix (founded 1983) and NOTIS were both acquired by Ameritech and merged into Ameritech Library Services in 1994.

Software · library systemActivePaid / subscription

Horizon · SirsiDynix

Descended from an internal Dynix project called Marquis. SirsiDynix announced in 2007 that it would consolidate on Unicorn (later rebranded Symphony), but its current Horizon page describes active development and continuous support, so Horizon cannot be filed with the historical systems above.

Software · library systemLegacyPaid / subscription

Voyager & Aleph · Ex Libris legacy ILS

Voyager was built by Endeavor Information Systems, founded by the same people who had been developing NOTIS's own abandoned client/server successor. Ex Libris acquired Endeavor in 2006; both Voyager and Aleph are in a migration period, with Ex Libris offering dedicated migration paths to Alma; Ex Libris support documentation still lists both products, and sunset dates vary by product, so confirm them with the vendor. Syracuse, for instance, retired a Voyager instance running since 1997 in 2024.

Software · library systemActivePaid / subscription

Alma · Ex Libris (Clarivate)

The explicit migration target for Voyager and Aleph; among the largest recent moves, the British Library moved to Alma following its October 2023 ransomware attack. Its AI Metadata Assistant and normalization rules are listed in Section VIII.

Software · library systemActivePaid / subscription

SirsiDynix Symphony / BLUEcloud

Symphony (Unicorn's eventual rebrand) is the flagship ILS of the Sirsi/Dynix family, paired since 2013 with the web-based BLUEcloud suite of applications; the two are a system and its application suite, not interchangeable names.

Software · library systemActivePaid / subscription

OCLC WorldShare Management Services (WMS)

OCLC's own LSP, distinct from Connexion/Record Manager, the cataloging client (Section VIII).

Software · library systemActiveOpen source

FOLIO

Open-source LSP built through a broad library-community collaboration.

Software · library systemActiveOpen source

Koha

One of the most widely deployed open-source ILS in the world.

Software · library systemActivePaid / subscription

Sierra · Innovative Interfaces (Clarivate)

The other major commercial player alongside Alma and Symphony; still receives active development and support, often paired with Clarivate's Vega discovery layer.

Current-awareness pointer

Everything in this section goes stale quickly — vendor consolidation, sunsets, and market share shift year to year. Marshall Breeding's annual Library Systems Report (usually published in American Libraries; the 2026 edition ran through Library Technology Guides directly, returning to American Libraries in 2027) is the field's own mechanism for tracking this, and librarytechnology.org hosts the full run of reports plus the deeper vendor history behind the lineage entries above — one link absorbing both the current snapshot and the historical archive.
XII

Discovery interfaces & services

Two kinds of discovery sit here: library discovery layers and connectors, and services for scholarly discovery and exploration. The first is the unified search patrons actually use — sitting on top of, or in place of, the local catalog. This section is the practical consequence of the section before it: once a vendor-maintained central index does the heavy lifting of aggregating and normalizing article- and e-resource-level metadata, a cataloger's daily work shifts from original description toward troubleshooting, mapping, and curating metadata that arrives already made from elsewhere — metadata management rather than cataloging, in a phrase several working catalogers now use about their own jobs.

Library discovery layers & connectors

Unified search over a library's own holdings and licensed content, and newer connectors that bring the same records into other interfaces.

Software · discoveryActivePaid / subscription

EBSCO Discovery Service (EDS)

A widely used index-based discovery service; adoption comparisons across vendors shift from year to year and depend on which libraries are counted. Built around a large, EBSCO-maintained central index of licensed article and e-resource content that patrons search alongside local holdings in one box.

Software · discoveryActivePaid / subscription

Ex Libris Primo (VE)

Tightly integrated with Alma (Section XI); Primo VE eliminates the separate Primo back office entirely, configuring discovery through Alma directly. Primo VE is the Alma-integrated edition of Primo; Primo and Summon (formerly Serials Solutions) are distinct Ex Libris discovery products.

Software · discoveryActivePaid / subscription

OCLC WorldCat Discovery

The natural discovery-layer pairing for OCLC WorldShare Management Services (Section XI), built on WorldCat's own shared bibliographic data.

Software · discoveryActiveOpen source

VuFind

An open-source library discovery interface. It is one common choice for FOLIO (Section XI), which ships with no patron-facing search of its own and has to be paired with a discovery layer. Libraries often pair open-source interfaces with a commercial central index anyway — EBSCO sells EDS integration for VuFind — and an open-source interface does not automatically mean open data underneath.

Software · discoveryActiveOpen source

Blacklight

An open-source discovery interface framework, widely used in academic libraries and digital collections. As with VuFind, an open-source interface does not automatically mean open data underneath, and libraries may pair it with a commercial central index.

Service · discoveryEmergingRestricted

Yale Library AI Connector · Yale University Library

Connects AI assistants that support the Model Context Protocol (MCP), with Claude and ChatGPT named as the most reliable, to Yale Library's catalog (almost 15 million records) and digital collections (nearly 185,000 records) through the library's MCP server, so researchers can request library resources within an AI conversation. Opened to the Yale community for beta testing on 15 October 2026, after staff testing and a fall 2025 student diary study. Retrieval covers catalog and digital-collections records, not licensed articles or article databases such as JSTOR and EBSCO. Emerging describes development: the service is in beta. Access is Restricted: use is limited to the Yale community. The software license was not verified, and AI-platform requirements and licensing should be assessed separately from eligibility. A useful example of AI-mediated discovery built on curated library metadata, distinct from AI-assisted cataloging (Section VIII): library metadata, then a retrieval connection, then an AI assistant, then the researcher. Grounding retrieval in library records is not an independent evaluation of every resulting answer. Checked 18 October 2026.

See also: AI Metadata Assistant (Section VIII), VuFind.

Scholarly discovery & exploration

Beyond the library's unified search interface, how can users discover scholarship through subjects, citations, identities, and other relationships? These services help users find and contextualize scholarship through disciplinary indexing, citation relationships, topic maps, and scholarly knowledge graphs. They are grouped here by their discovery function and are not interchangeable with the library discovery layers above.

Service · knowledge baseActiveOpen data / content

OpenAlex

A free, open index of the global research system: works, authors, institutions, sources, topics, publishers, and funders, linked to one another and to DOIs, ORCID iDs, and ROR IDs. Built by the nonprofit OurResearch as a successor to Microsoft Academic Graph, it offers a web interface, an API (free, with a free API key), and monthly bulk snapshots; the data is CC0. Annotated here both as a scholarly index and as reusable metadata infrastructure: Pinakes, for one, draws its institutional affiliations from it. The infrastructure example: how identifiers and entity relationships make metadata reusable across applications.

See also: ORCID (Section III), Wikidata (Section VII), Pinakes.

Software · discoveryActiveOpen source

Scholia

Visual scholarly profiles of researchers, organizations, venues, works, and topics, generated on the fly by SPARQL queries against Wikidata. The code is open source (GPL-3.0), and the web app runs on Wikimedia Toolforge. Profiles show only what Wikidata records, so gaps in Wikidata's coverage of the scholarly literature become gaps in Scholia, and the Toolforge instance currently notes that it can reach only part of the data after changes to the Wikidata Query Service, with a fuller mirror under evaluation; check its banner before demonstrating it. The clearest linked-data example: students can connect an interface to the structured statements and queries behind it.

See also: Wikidata (Section VII), SPARQL (Section XIII).

Service · discoveryActiveFree to access

Open Knowledge Maps

A free visual search engine from a Vienna-based nonprofit. A keyword search gathers about 100 relevant documents from BASE (all disciplines) or PubMed (life sciences) and clusters them into a knowledge map of topic areas using the similarity of their metadata. The project shares its source code, content, and data under open licenses. The useful contrast: relationships computed from textual similarity, not from citations or explicitly recorded subject relationships.

See also: Pinakes, OpenAlex.

Service · discoveryEmergingFree to access

Pinakes · Rhetoric & Composition

A free disciplinary index of scholarship in rhetoric, composition, writing studies, and technical communication, covering more than 50,000 articles from 54 journals and about 800 scholarly books, hosted by the WAC Clearinghouse. Built by Justin Lewis (Olympic College), who describes it as a personal scholarly tool shared publicly rather than peer-reviewed infrastructure. It updates from Crossref, RSS feeds, and web scraping; assigns each article topics automatically from a 61-term disciplinary vocabulary; and combines subject browsing with citation exploration, author profiles, co-authorship and citation networks, and a coverage page explaining which journals deposit reference data. Not to be confused with the IRHT's Pinakes database of Greek manuscripts. Emerging describes development: its developer presents it as a one-person scholarly tool rather than peer-reviewed infrastructure, and it is still changing, having moved to WAC Clearinghouse hosting in September 2026 while adding coverage and tools, which a What's New page tracks. The disciplinary-design example: someone selects a corpus and builds a particular representation of a field, and metadata aggregation, automated subject assignment, and coverage gaps all shape what can be discovered.

See also: Eunomia's Labors (Section III), Open Knowledge Maps, OpenAlex.

XIII

Retrieval & interoperability protocols

How systems query and harvest each other's records.

Standard · protocolLegacyFree to access

Z39.50 · NISO/ANSI Z39.50, also ISO 23950

The Library of Congress is the Maintenance Agency and Registration Authority for both the NISO and ISO editions, which are technically identical. Still present in many ILS platforms, but less used in new development than SRU and REST APIs.

Standard · protocolActiveFree to access

SRU / SRW · Search/Retrieve via URL / Web Service

A more web-native alternative to Z39.50 for structured search. SRU and SRW are related but distinct bindings of the same search model, so check which one a system supports.

Standard · protocolActiveFree to access

OAI-PMH · Open Archives Initiative Protocol for Metadata Harvesting

The harvesting protocol underlying interoperability across the repository platforms in Section X (EPrints, DSpace, Invenio all comply with it).

Standard · linked dataActiveFree to access

SPARQL

The W3C query language for RDF data, used to query linked-data endpoints such as the Wikidata Query Service.

See also: Scholia (Section XII).

XIV

Standards organizations & practical validation tools

The bodies that set the standards above, and the tools that check whether an implementation actually conforms to them. Access labels do not apply to the organizations themselves; the standards each one publishes carry their own terms.

OrganizationActiveNot applicable

NISO · National Information Standards Organization

OrganizationActiveNot applicable

W3C · World Wide Web Consortium

OrganizationActiveNot applicable

ISO · International Organization for Standardization

ISO standards documents themselves are typically sold, unlike most of the NISO/W3C output above.

OrganizationActiveNot applicable

DCMI · Dublin Core Metadata Initiative

OrganizationActiveNot applicable

Creative Commons

The nonprofit behind the Creative Commons licenses, the licensing framework this site itself uses (CC BY-NC-SA 4.0, carried in every Infophilia-ecosystem footer).

See also: RightsStatements.org, Local Contexts (Section XV).

Service · web toolActiveFree to access

License Chooser · Creative Commons

A practical companion to the licensing framework: the Chooser generates standardized, machine-readable license markup rather than requiring hand-written HTML.

VocabularyActiveFree to access

RightsStatements.org

A small set of standardized rights statements that libraries, archives, and museums use to tell online visitors the copyright and reuse status of digital objects. Each statement has its own URI, which institutions store in a rights element of the record. Unlike Creative Commons licenses, the statements grant no permission; they give information, and they cover cases where the institution does not hold the rights. Launched in 2016 by Europeana and the Digital Public Library of America, and used by aggregators including both; since April 2026 its organizational home is Digital Scholar, the nonprofit behind Omeka and Zotero. Reuse terms for the statements themselves were not checked for this edition.

See also: Creative Commons, Local Contexts (Section XV).

Software · metadata toolActiveFree to access

schema.org Markup Validator and Google's Rich Results Test

Two distinct, complementary checks: the schema.org validator (successor to Google's old Structured Data Testing Tool) checks markup against the schema.org vocabulary across JSON-LD/RDFa/Microdata (a clean result is not a guarantee of full specification compliance or of search eligibility); the Rich Results Test checks Search-eligibility specifically, a narrower question. Both are what this site's own JSON-LD is checked against to reach zero errors and zero warnings.

See also: SHACL Playground.

Software · metadata toolActiveOpen source

SHACL Playground · Zazuko

A browser-based place to write SHACL shapes, paste in RDF data, and examine the validation results. Validation runs entirely client-side in JavaScript, so nothing is uploaded. Released as open source under the AGPL. It lets students run validation rather than only read about it; pair it with SHACL (Section VII) and DCTAP (Section II).

See also: SHACL (Section VII), DCTAP (Section II).

XV

Critical & reparative cataloging

Practical tools and community-maintained vocabularies for naming and repairing the moral and political consequences of classification — the tool-shaped counterpart to Core Readings' critique-shaped Section III.

Community resourceActiveFree to access

Cataloging Lab

Moved here from Core Readings' Section III, where it sat among scholarly critiques (Berman, Drabinski, Olson) despite being a toolkit rather than a reading. Clearinghouse for reparative-cataloging proposals, subject-heading change advocacy, and community documentation of practice.

Vocabulary · thesaurusActiveFree to access

Homosaurus

The anchor vocabulary of the reparative-cataloging movement, used for LGBTQIA+ subject access alongside broader reparative-description work at institutions including Harvard's HOLLIS.

Classification schemeActiveMixed

Brian Deer Classification · Xwi7xwa Classification

The Brian Deer Classification System, developed by a Kahnawake Mohawk librarian, and UBC's Xwi7xwa Classification are alternatives to LCC/DDC built to organize materials about Indigenous peoples from an Indigenous perspective, adopted and adapted by several tribal and First Nations libraries. Public descriptions are freely available; reuse terms and cultural authority over these schemes rest with the communities and institutions that maintain them, so check with them before adapting.

See also: Local Contexts.

Community resourceActiveFree to access

Local Contexts · Traditional Knowledge & Biocultural Labels and Notices

An initiative supporting Indigenous data sovereignty. Indigenous communities customize Traditional Knowledge (TK) and Biocultural (BC) Labels to state their own rules for attribution, access, and use of cultural heritage and data, and institutions and researchers apply Notices; both are created through the Local Contexts Hub and can be carried into systems such as Omeka S (through a module), Mukurtu, and DataCite metadata. The point for metadata work: authority over reuse rests with the community, not the holding institution, a question Creative Commons licenses and RightsStatements.org do not settle. Public descriptions are free to read; Hub account terms were not checked for this edition.

See also: RightsStatements.org (Section XIV), Brian Deer Classification, Omeka Classic and Omeka S (Section IX).

Service · catalogActiveFree to access

ZineCat · the Zine Union Catalog

A union catalog for zines, grown out of a CUNY Graduate Center Digital Humanities capstone project — explicitly framed by its own community as “an open source WorldCat specifically for zines,” since zine holdings are inconsistently represented in WorldCat itself. The catalog runs on the open-source CollectiveAccess software below; the software’s license does not by itself make the catalog’s records open.

Vocabulary · thesaurusActiveFree to access

Zine Subject Thesaurus

A companion vocabulary built because zines resist LCSH: a hierarchical thesaurus its maintainers describe as more accessible, current, and radical than standard subject thesauri. A concrete case, alongside Homosaurus above, of a community building its own vocabulary because the standard one doesn’t serve its materials. Check the maintainers’ terms before reusing it.

Software · digital collectionsActiveOpen source

CollectiveAccess

Open-source collections-management software, the platform ZineCat is built on. Listed separately because the software, the catalog data, and the thesaurus each carry their own terms.

§

Professional organizations & lists

Domain societies and active communities for following how this field changes. ALA Core itself, BARTOC, the ISKO Encyclopedia, and the LC/PCC portals stay in Core Readings’ Professional Resources section; this section points to the groups inside ALA Core most relevant to this field, plus communities beyond ALA. Groups are listed here when their principal contribution is discussion, peer assistance, announcements, community participation, or historical stewardship of foundational knowledge-organization work; groups that maintain specifications, software, vocabularies, or datasets appear with that work in the relevant section. Group schedules, memberships, and activity change often, so check each one’s own page.

  • Music Library Association (MLA) — the domain society for music cataloging and librarianship.
  • Society of American Archivists (SAA) — the domain society for archival description and practice.
  • IFLA — International Federation of Library Associations and Institutions.
  • Madras Library Association (MALA) — India's oldest library association, founded in 1928 with S. R. Ranganathan as its founding general secretary. MALA first published his Five Laws of Library Science (1931), Colon Classification (1933), and Prolegomena to Library Classification (1937), and remains an active professional association in Chennai. See Colon Classification, Section IV.
  • Sarada Ranganathan Endowment for Library Science (SRELS) — the endowment founded by S. R. Ranganathan in Bengaluru to improve library and information services in India; it organizes lecture series, workshops, and seminars, published the seventh edition of Colon Classification (1987), and publishes the Journal of Information and Knowledge (formerly the SRELS Journal of Information Management).
  • AutoCat — long-running international discussion list devoted to cataloging and authority control, still active.
  • jESSE — discussion list for library and information science educators, now hosted at Wayne State University after moving from its original University of Tennessee host.
  • ALA Core interest groups and committees — Core: Leadership, Infrastructure, Futures was formed in September 2020 from ALCTS, LITA, and LLAMA, so the cataloging and metadata groups that once sat in ALCTS now sit inside Core alongside technology and leadership groups (see Core Readings for the division itself). For this field, start with these interest groups: Bibliographic Conceptual Models, Linked Data, Metadata, Cataloging and Classification Research, Faceted Subject Access, Authority Control, and Artificial Intelligence and Machine Learning in Libraries. The committees to watch are Cataloging: Description and Access (CC:DA) and the Subject Analysis Committee (SAC). Interest groups are the lower-commitment way in.
  • CILIP Metadata & Discovery Group (MDG) — the UK special interest group for metadata and discovery across cultural institutions, commerce, and publishing, formerly the Cataloguing & Indexing Group. It advises CILIP on bibliographic control, works with regional groups on training and a biennial conference, and publishes Catalogue & Index.
  • LD4 community — the mailing list and Slack community for linked data in libraries, where projects such as the MARC21 to LRM/RDA/RDF mapping post announcements.
  • LD4 Wikidata Affinity Group — a discussion group on how libraries can use Wikidata to publish, link, and enrich linked data, with a mailing list and a Slack channel. Its program page describes biweekly calls; check that the schedule is current.
  • Wikimedia and Libraries User Group — the Wikimedia community for library work on Wikidata and the other Wikimedia projects.
  • RDA Toolkit regions — RDA’s regional sections (Africa, Asia, Europe, Latin America and the Caribbean, North America, Oceania), with announcements, governance, and meeting notes, plus an RDA Discussion List, a newsletter, and the RDA Lab Series.
  • SAA Description Section — a forum for archival description, open to SAA members; publishes the Descriptive Notes newsletter.
  • SNACSchool — training in creating, editing, and merging SNAC records, with recordings of past sessions posted publicly. See SNAC in Section VI.
❦

Provenance & project history

The Knowledge Structures Toolbox was developed in 2001–2002 for teaching information organization at the University of Arizona, connecting concepts, sources, and tools for reusable instruction. Its commons-oriented premise informed later work in metadata education, including the Metadata Education and Research Information Commons (MERIC).

MERIC was a proposed collaborative teaching-and-research commons for metadata education. Anita S. Coleman led development of its proof-of-concept clearinghouse. A University of North Texas prototype by William Moen and his class followed, but the initiative did not become a sustained production service.

The 2026 renewal splits the original Toolbox's single register into two siblings: Core Readings, an annotated bibliography of what to read and discuss, and this page, a directory of what to consult and use. Where the two overlapped — professional organizations, project tools flagged inside reading sections — entries were reconciled rather than duplicated, and that reconciliation is itself part of this page's provenance.

On this edition

This is a teaching resource, offered openly for reuse and adaptation, maintained as a dated, citable record. As of this edition (version 1.0), it contains 131 annotated entries across fifteen sections, plus 15 professional organizations and discussion lists, and a task index of 10 routes through them. An entry names one resource, or a closely related group when the same labels accurately describe all its members. Where the labels would conceal an important difference, resources receive separate entries or an explicit qualification. Every entry has a stable identifier that is also its link on this page. Every entry, its three labels, its cross-references, and its task routes are also available as toolbox.csv, toolbox.json, and toolbox.md, and the repository carries a CITATION.cff file. The teaching note explains what each format is for, and a second teaching note, AI and linked data, unleashed, works through one developer’s metadata lifecycle with class activities.