A point or period of time associated with an event in the lifecycle of the resource.
Date may be used to express temporal information at any level of granularity. Recommended practice is to express the date, date/time, or period of time according to ISO 8601-1 or a published profile of the ISO standard, such as the W3C Note on Date and Time Formats or the Extended Date/Time Format Specification.
dc:date is the only date field in simple Dublin Core, which makes it overloaded. Its definition is deliberately loose: a point or period of time associated with an event in the lifecycle of the resource. Creation, publication, revision, digitization and accession are all lifecycle events, and the element does not say which one a given value refers to.
Which event the value belongs to
Most collections settle on one meaning and write it into their cataloging guidelines. For published material that is usually the publication or issue date, because it is the date a citation uses and the one a reader filtering by year expects. Photographs and manuscripts tend to use the creation date.
Born-digital files are harder. A file system timestamp shows when a particular copy was last written, which can be years after the content was made, and copying that timestamp into dc:date without checking is one of the most frequent errors in harvested records.
If a record needs several dates, the element can repeat. Nothing distinguishes one value from another, though. A harvester seeing 1987 and 2019 in the same record cannot tell which is the original work and which is the scan, and that gap is the main reason qualified Dublin Core exists.
Writing the value: ISO 8601, W3CDTF and EDTF
DCMI recommends ISO 8601 or a published profile of it. The profile cited most often is the W3C Note on Date and Time Formats (W3CDTF) from 1997, which narrows ISO 8601 to six levels of granularity. The Extended Date/Time Format (EDTF), maintained by the Library of Congress, adds notation for uncertain and approximate dates.
| Granularity | W3CDTF pattern | Example |
|---|---|---|
| Year | YYYY | 1997 |
| Year and month | YYYY-MM | 1997-07 |
| Complete date | YYYY-MM-DD | 1997-07-16 |
| Date and time | YYYY-MM-DDThh:mmTZD | 1997-07-16T19:20+01:00 |
The value of a standard form is that it sorts and filters. “16 July 1997”, “07/16/97” and “Summer 1997” describe roughly the same moment, but only the ISO form orders correctly and survives a trip through a database. A friendlier display string can always be generated from it later; the reverse is unreliable.
When only the year is known, record only the year. Padding it to 1997-01-01 invents a precision that later users will take at face value.
Periods, open ends and uncertainty
A period is written as two dates separated by a slash: 1914/1918, or 1997-03/1997-06 for a span of months. Either end may be left empty, so 1960/ describes something that starts in 1960 with no known end. EDTF adds 1984? for an uncertain year and 1950~ for an approximate one. Those forms only help if every system that reads the records understands EDTF, so it is worth testing a sample export before adopting them across a collection.
A common confusion is putting the period a resource is about into dc:date. A 2005 history of the First World War has a date of 2005; 1914–1918 is its temporal coverage and belongs in dc:coverage or dcterms:temporal.
Refinements in the dcterms namespace
DCMI Metadata Terms resolves the ambiguity with sub-properties of dcterms:date: dcterms:created, dcterms:issued, dcterms:modified, dcterms:available, dcterms:valid, dcterms:dateAccepted, dcterms:dateCopyrighted and dcterms:dateSubmitted. Each names the lifecycle event it records. Because they are sub-properties, software that understands only the generic date can still read every one of them as a date.
For a preservation record a useful combination is dcterms:created for the original work, dcterms:issued for its publication and dcterms:modified for the last change to the file being described. Alongside dc:creator and dc:publisher that answers who made a resource and when it reached the public.
The trade-off appears at export time. Mapped down to simple Dublin Core for OAI-PMH, all three refinements become repeated dc:date values, and a portal that shows a single date per record has no way of knowing which one mattered. Ordering the exported values deliberately, with the most meaningful date first, is a cheap safeguard.
Example in RDF
@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
<https://example.org/photos/harbour-1962.tif>
dc:title "Harbour at low tide" ;
dc:date "1962-08" ;
dc:creator "Moreau, Claire" .
<https://example.org/reports/survey-2019.pdf>
dcterms:created "2018-11-02" ;
dcterms:issued "2019-01-15" ;
dcterms:modified "2023-06-30" .
Questions about dc:date
What does dc:date mean in Dublin Core?
dc:date records a point or period of time linked to some event in the resource's lifecycle. Collections usually fix one meaning locally, most often the publication date for published material and the creation date for photographs, manuscripts and unpublished files.
Which date format should dc:date use?
DCMI recommends ISO 8601 or a profile of it such as W3CDTF. That means forms like 1997, 1997-07 or 1997-07-16, which sort correctly and can be validated. Display formats like 16 July 1997 belong in the user interface.
How is a date range written in dc:date?
Use two ISO 8601 dates separated by a slash, for example 1914/1918 or 2001-03/2001-09. The DCMI usage comment allows either end of the range to be left open when it is unknown.
Can a record contain more than one dc:date?
Yes, the element is repeatable. The weakness is that simple Dublin Core gives no way to say which value is creation and which is publication, so qualified records use dcterms:created, dcterms:issued or dcterms:modified for that.
Should dc:date hold the period a resource is about?
No. A 2005 book about the 1920s has a date of 2005. The period it discusses is temporal coverage and belongs in dc:coverage or dcterms:temporal, which keeps date searches from returning books by their subject period.