Skip to content
Property · DCMI Metadata Terms: properties

dct:source meaning: stating that one resource derives from another

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

A related resource from which the described resource is derived.

The described resource may be derived from the related resource in whole or in part.

The dct: prefix used in DCAT files and many W3C specifications points to DCMI Metadata Terms, and dct:source is that vocabulary’s statement of derivation. It shares its definition with the original dc:source element, a related resource from which the described resource is derived, and the comment adds that the derivation may be whole or partial. What changes in the dcterms version is its position in the vocabulary and the shape of its values.

Position in the vocabulary

dcterms:source is declared a sub-property of two terms: dc:source and dcterms:relation. The first keeps it compatible with simple Dublin Core, so a crosswalk to oai_dc maps it directly to the old element. The second places it in the relation family, alongside isPartOf, isVersionOf, isFormatOf and the rest, which means any software that understands only the generic relation still sees a link.

Unlike most of its siblings, source has no inverse in the vocabulary. There is no isSourceOf. A record for an original manuscript cannot point forward to its transcripts with a DCMI term; the link is only stated from the derivative’s side, and a query has to search in that direction.

Values as resources

The current DCMI documentation notes that the property is intended for non-literal values. In Turtle that means a URI in angle brackets, as in the example; in RDF/XML an rdf:resource attribute. A citation string or a shelfmark typed as a literal still appears in many records, especially those converted from older formats, but it creates a dead end. The derived file points to text that looks like a reference and cannot be followed.

Where the source has no URI of its own, the usual remedy is to mint one: create a minimal record for the original, give it an identifier and a title, and point to it. That record can later be enriched without touching any of the derivatives. It also gives every derivative of the same original a shared target, so a query for everything made from one manuscript returns transcripts, excerpts and translations together.

Derivation with change

The property is most useful when the content changed on the way. Typical cases:

Derived resource Source
Transcript or OCR text page image or audio recording
Excerpt or clip full document or full recording
Aggregated or cleaned dataset raw data files
Translation text in the original language

When nothing changed except the encoding, dct:isFormatOf says more. A lossless TIFF to JPEG access copy keeps the image and changes the format; OCR keeps neither the format nor the visual layout. The first is a format relationship, the second a derivation. Many repositories apply both properties to borderline cases, which is acceptable because they do not contradict each other.

Where dct:source stops

A single triple records that derivation happened. It does not say when, by whom, with what software or with what parameters. For a scan made in 2012 that is often enough. For a dataset computed from raw sensor output, the method usually matters as much as the input, and reproducibility depends on it.

The W3C PROV ontology covers that gap with prov:wasDerivedFrom, activities and agents, and it maps cleanly onto the simple case: a dct:source statement can be read as a short form of prov:wasDerivedFrom with no activity attached. Projects publishing research data often keep dct:source for catalog-level discovery and the PROV graph for the full lineage. Preservation systems record the same facts as PREMIS events, linking the derived object, the original and the migration or transformation that produced it, with the software version that ran it.

Example in RDF

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

<https://example.org/transcripts/council-minutes-1911-03.txt>
    dct:title "Transcript of council minutes, March 1911"@en ;
    dct:format "text/plain" ;
    dct:source <https://example.org/scans/council-minutes-1911-03.tif> .

<https://example.org/data/station-14-daily.csv>
    dct:source <https://example.org/data/station-14-raw-2024.nc> .

Questions about dcterms:source

What does dct:source mean?

dct:source, also written dcterms:source, states that the described resource was derived from another resource, wholly or in part. A transcript derived from a scan, a daily summary computed from raw sensor data or an excerpt cut from a recording all have a source.

How is dcterms:source different from dc:source?

The definitions match. dcterms:source is a sub-property of dc:source and of dcterms:relation, and it is intended for non-literal values, so in linked data it points to the related resource by URI. dc:source is often used with literal strings.

When is isFormatOf better than dct:source?

When the derivative is substantially the same resource in another format, such as a JPEG access copy of a TIFF master. dct:source fits when the content changed in the process, as with transcription, selection, aggregation or translation.

Can a resource have several sources?

Yes. A compiled dataset drawn from three surveys, or an anthology of excerpts, has one dct:source statement per contributing resource. The property does not record how much was taken from each, which belongs in a description or provenance note.

Is dct:source a provenance property?

It records one specific provenance fact, derivation, but not custody history, agents or activities. Projects that need a full lineage chain often combine it with, or replace it by, prov:wasDerivedFrom and related terms from the W3C PROV ontology.

More from DCMI Metadata Terms: properties

All 13 in this group