Reference Glossary
Dublin Core
A 15-element metadata vocabulary (Title, Creator, Subject, Description, Publisher, Contributor, Date, Type, Format, Identifier, Source, Language, Relation, Coverage, Rights) from 1995 for describing digital resources.
Why it matters in a DAM
Dublin Core is the closest thing DAM has to a lowest-common-denominator schema — many platforms (ResourceSpace, various open-source and library-oriented DAMs) ship it as the default field set out of the box, and it's the schema most often used as the target or source in a metadata crosswalk when a DAM needs to exchange records with library, archive, or repository systems. Its simplicity is also its limit: 15 flat elements can't express relationships like 'this image documents that physical artwork,' which is why art- and museum-focused DAMs layer VRA Core or CDWA on top of it rather than relying on it alone.
A worked example
Common mistake
Treating 'Coverage' and 'Relation' as optional filler and leaving them blank, which discards the ability to record an asset's spatial or temporal scope, or to link it to related versions, derivatives, or the physical object it depicts.
Dublin Core originated at a joint workshop held by OCLC and the NCSA in Dublin, Ohio, in March 1995, where more than 50 librarians, archivists, and web standards specialists worked out a minimal set of elements that could describe almost any web-based resource well enough to make it findable. The 15-element result was formalized as the Dublin Core Metadata Element Set and published as RFC 2413 in 1998, and it continues to be maintained by the Dublin Core Metadata Initiative (DCMI).
The design goal was deliberately narrow: every element is optional, repeatable, and free of any assumption about the resource’s type, which is what let Dublin Core spread across libraries, archives, government repositories, and later DAM systems without modification. That same simplicity is why it rarely stands alone in a DAM handling rich media — a photo library needs technical fields (resolution, color space, camera model) and rights fields far more granular than Dublin Core’s single flat ‘Rights’ element, so most DAM schemas extend Dublin Core rather than replacing it.
In practice, Dublin Core matters to DAM teams mainly at the boundary between systems: when exporting to a digital repository, an institutional archive, or any system that expects OAI-PMH harvesting (which uses unqualified Dublin Core as its baseline format), a DAM needs a reliable crosswalk from its own schema down to these 15 elements, even if its internal working schema is much richer.
Frequently asked
What is Dublin Core?
A 15-element metadata vocabulary — Title, Creator, Subject, Description, Publisher, Contributor, Date, Type, Format, Identifier, Source, Language, Relation, Coverage, Rights — created in 1995 for describing digital resources.
Why do many DAM platforms ship Dublin Core as a default schema?
It's the closest thing DAM has to a lowest-common-denominator schema — platforms like ResourceSpace and various open-source or library-oriented DAMs ship it out of the box, and it's the schema most often used as the target or source in a metadata crosswalk when exchanging records with library, archive, or repository systems.
What is Dublin Core's main limitation?
Its simplicity is also its limit — 15 flat elements can't express relationships like 'this image documents that physical artwork,' which is why art- and museum-focused DAMs layer VRA Core or CDWA on top of it rather than relying on it alone.
Which Dublin Core fields are most often left blank, and why does that matter?
'Coverage' and 'Relation' are commonly treated as optional filler and left blank, which discards the ability to record an asset's spatial or temporal scope, or to link it to related versions, derivatives, or the physical object it depicts.
Is Dublin Core sufficient for museum or archive DAM use cases on its own?
Not typically — its flat structure can't capture relationships between a physical work and its digital surrogates, which is why cultural-heritage DAMs usually pair it with a richer standard like VRA Core rather than using it standalone.
How many core elements does Dublin Core define?
Fifteen — covering everything from Title and Creator through Rights and Coverage, forming a broad but flat descriptive vocabulary.
Sources
- Dublin Core originated at a March 1995 OCLC/NCSA workshop in Dublin, Ohio, attended by over 50 participants. checked 2026-08-07 — DCMI: DCMI History
- The 15-element Dublin Core vocabulary consists of Title, Creator, Subject, Description, Publisher, Contributor, Date, Type, Format, Identifier, Source, Language, Relation, Coverage, and Rights. checked 2026-08-07 — Dublin Core — Wikipedia
- The original 15-element vocabulary was published as RFC 2413, 'Dublin Core Metadata for Resource Discovery,' in 1998. checked 2026-08-07 — DCMI: DCMI History