The set of labeled concepts specified by the Library of Congress Subject Headings.
Subject access is the part of description where personal vocabulary does the most damage. One cataloger writes “tape decay”, another “magnetic tape degradation”, and a search for either finds half the collection. dcterms:LCSH addresses that by naming a shared source: the Library of Congress Subject Headings. In DCMI terms it is a vocabulary encoding scheme, and its definition is short: “the set of labeled concepts specified by the Library of Congress Subject Headings”.
What the scheme signals
The scheme does not hold any headings itself. It works as a label on a value that says “look this up in LCSH”. On dcterms:subject, that turns a free string into a controlled one. An aggregator receiving records from a hundred libraries can then treat matching headings as the same concept and offer them as a facet without guessing, and can follow them into the authority file for related terms.
In XML profiles the scheme appears as xsi:type="dcterms:LCSH". In RDF, the DCMI Abstract Model pattern uses a value node with dcam:memberOf dcterms:LCSH and the heading in rdf:value, as in the example. A third pattern skips both and points directly to the heading’s URI at id.loc.gov, where membership in LCSH is evident from the URI itself.
Headings, subdivisions and the double hyphen
LCSH headings are often built from parts. “Magnetic tapes—Deterioration” combines a topical heading with a topical subdivision. Geographic, chronological and form subdivisions follow the same pattern, for example “Photography—France—History—19th century”. Library systems store these parts in separate MARC subfields; when a record is crosswalked to Dublin Core, the parts are joined with two hyphens.
Two things follow. First, a pre-coordinated string like that is still a valid LCSH value even if it does not exist as one authority record, because subdivisions are combined under documented rules. Second, splitting the string back into parts is possible but lossy if the separator was rewritten as a single hyphen or an em dash, which happens surprisingly often in hand-edited spreadsheets.
LCSH as linked data
Since 2009 the Library of Congress has published LCSH at id.loc.gov. Each heading has a URI of the form http://id.loc.gov/authorities/subjects/sh… and is modeled in SKOS: a skos:prefLabel for the authorized form, skos:altLabel for the “Used For” references, and broader and narrower links. The SKOS Core vocabulary describes those properties.
For a digital collection, storing the URI next to the label gives two advantages. Revised headings keep their identifier, so a record pointing to the URI picks up the new label without being edited; LCSH replaced “Illegal aliens” with “Noncitizens” in 2021, and every URI-based record followed. And the SKOS relations allow a search for a broad topic to expand to narrower headings.
When LCSH is not the right fit
LCSH was designed for general library collections in English. Specialist archives often find it too coarse in their own domain and too detailed elsewhere. Art collections may use the Getty Art and Architecture Thesaurus; medical libraries use MeSH, which DCMI also lists as an encoding scheme. A record can carry several dcterms:subject statements from different schemes, each marked with its source.
Mixing uncontrolled keywords into the same field with the LCSH scheme declared on them is the error to avoid: a heading checker will reject every invented term, and a harvester that trusts the scheme will index them as authorized headings.
Example in RDF
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix dcam: <http://purl.org/dc/dcam/> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
<https://example.org/theses/2019-044.pdf>
dcterms:title "Moisture damage in early magnetic tape" ;
dcterms:subject [
dcam:memberOf dcterms:LCSH ;
rdf:value "Magnetic tapes--Deterioration"
] .
Questions about dcterms:LCSH
What is LCSH?
LCSH, the Library of Congress Subject Headings, is a controlled vocabulary of subject terms maintained by the Library of Congress since the late nineteenth century. It is used by libraries worldwide to describe what books, articles and other resources are about.
What does dcterms:LCSH do in a record?
It identifies LCSH as the source of a subject value. Attached to dcterms:subject, it tells harvesters that 'Magnetic tapes--Deterioration' is an authorized LCSH heading, not a keyword someone typed, so it can be matched against the authority file.
Should I record LCSH as a string or a URI?
Both are common. A string marked with the LCSH scheme suits OAI-PMH and XML profiles. Linked data works better with the id.loc.gov URI of the heading, which stays stable when the preferred label is revised.
Is LCSH available as SKOS?
Yes. The Library of Congress publishes LCSH at id.loc.gov as linked data, and each heading is modeled as a skos:Concept with a preferred label, alternative labels for unused forms, and broader and narrower relations.
Why do some LCSH headings use double hyphens?
The double hyphen separates a main heading from its subdivisions, such as topical, form, chronological or geographic subdivisions. In MARC the parts sit in separate subfields; flattening them for Dublin Core joins them with '--'.