Skip to content
Property · DCMI Metadata Terms: properties

dct:title guide: names, subtitles and alternative titles in DCMI Terms

Published Formatory editorial team
http://purl.org/dc/terms/title

A name given to the resource.

A file without a usable title is a file nobody finds twice. Of the properties in the DCMI Metadata Terms namespace, dct:title (written dcterms:title in most library documentation) does the most work in search results and the least work in the specification: it is defined as a name given to the resource, with no usage comment at all. The practical guidance comes from what the property’s range allows and from decades of cataloging habit.

A literal with a language

The declared range is rdfs:Literal. A title is a string, never a link to another resource, and that fits the way titles behave: they are the one human-readable label every record has to carry.

Literals in RDF can carry a language tag, and titles benefit more than most values. A Canadian government report has an English and a French title of equal standing; tagging each (@en, @fr) lets an interface show the right one without anyone deciding which is the translation. The language of the title can differ from the language of the content, too. A German study with an English title is common in scientific publishing, and its title is tagged @en even though the text is German.

Subtitles, alternatives and former titles

The convention in most cataloging is to record the title as it appears on the resource, including the subtitle, joined with a colon: “Harbour lights: a day on the waterfront”. dcterms:alternative, a sub-property of dcterms:title, then holds any other names the resource goes by:

  • a short form used in citations or on spines
  • an acronym or abbreviation
  • an earlier title for a renamed dataset or website
  • an informal translation that is not printed on the resource

Because alternative refines title, a system that ignores it can still treat its values as titles, which is useful for search and harmless for display. Linked-data projects sometimes use skos:altLabel for similar purposes on concepts, but for resources the DCMI property is the conventional choice.

Untitled resources

Born-digital collections are full of files that arrived without titles: camera images named IMG_0442.jpg, documents called final_v3.docx, audio from a recorder that numbers its files. Using the filename as the title is quick and leaves users with nothing to recognize.

Archival practice handles this with devised titles, written by the cataloger from the content. Standards such as DACS in the United States and ISAD(G) internationally expect devised titles for untitled material, and many institutions mark them with square brackets so that users can tell an assigned title from one found on the item. A devised title should be short and concrete: what the image shows, what the document is, who is speaking in the recording.

Situation Title approach
Title on the resource transcribe it, including subtitle
No title, content clear devise one, bracketed by local rule
Title misleading or wrong transcribe it, explain in a note
Many near-identical files devise a pattern plus a distinguishing detail

The third row is the one people skip. A title printed on a resource is evidence, even when it is wrong; correcting it silently loses that evidence. A description or note can explain the error while the title stays as found.

Titles alongside identifiers

Titles are not unique and were never meant to be. Two editions of a report can share a title word for word, and an archive can hold hundreds of items called “Minutes”. Distinguishing them is the job of the identifier, and grouping them is a matter for subject and series relationships. A practical test for a title is whether a user scanning a result list of twenty similar items can tell which one to open; a title that passes it rarely needs to carry a date or an accession number inside the string.

Example in RDF

@prefix dct: <http://purl.org/dc/terms/> .

<https://example.org/films/harbour-1958.mkv>
    dct:title "Harbour lights: a day on the waterfront"@en ;
    dct:title "Lumières du port"@fr ;
    dct:alternative "Harbour lights"@en .

<https://example.org/files/box-12/IMG_0442.jpg>
    dct:title "[Workers loading timber at the north quay]"@en .

Questions about dcterms:title

What is dct:title?

dct:title is the common prefixed form of dcterms:title, the DCMI Metadata Terms property for a name given to the resource. It is a sub-property of the original dc:title element and has a declared range of rdfs:Literal.

Should a subtitle be part of dct:title?

Usually yes, joined to the main title with a colon, since the subtitle is part of the name given on the resource. A short form without the subtitle can be recorded separately with dcterms:alternative for display or citation.

How are titles in several languages recorded?

Each language version is a separate literal with a language tag, such as @en and @fr. Interfaces can then select the title that matches the user's language, and none of the versions has to be marked as a translation in the string itself.

What title should an untitled file get?

A devised title written by the cataloger, describing the content briefly. Many archives place devised titles in square brackets to show they were not taken from the resource. A filename like IMG_0442.jpg is not a useful title.

What is the difference between dct:title and dcterms:alternative?

dct:title is the name given to the resource. dcterms:alternative, a sub-property of it, records any other name: abbreviations, translated titles used informally, former titles or series-level short forms. Both are literals.

More from DCMI Metadata Terms: properties

All 13 in this group