10. Publication Date (M)¶
10.2. Definition and Usage Instruction¶
A date associated with an event in the life cycle of the resource. Typically, Date will be associated with the creation or availability of the resource. Recommended best practice for encoding the date value is defined in a profile of ISO 8601 [W3CDTF] and follows the
The date should be formatted according to the W3C encoding rules for dates and times:
YYYY-MM-DD (e.g. 1997-07-16)
YYYY[four-digit year] is ‘’mandatory’‘
MM[two-digit month (01=January, etc.)] is ‘’optional’‘
DD[two-digit day of month (01 through 31)] is ‘’optional’‘
One date field – Date of Publication:
Often repository systems have more then one date fields that serve different purposes. Date of creation, publication, modified, promotion, etc. Preferably in the end-users perspective the most logical and meaningful date will be the date of publication.
No date of publication available:
If no date of publication is available, use any other date available. It is better to use one date than no date at all.
Additions like “Zulu time” should NOT be part of the metadata.
For fuzzy dates use a logical year that most represents that period, e.g.
1650 instead of
To express more about that temporal period, one can use the
dc:coverage field. A temporal period can be expressed in a standard way when precisely defined (see Coverage (R)) or when “fuzzy” or uncertain by free text expressions. A service provider is able to sort dates based on date standards like W3CDTF. Since there is no standard for fuzzy dates for terms like “Renaissance” or “17th Century”, they will simply not appear on date-based query results.
- introduced in DRIVER Guidelines v2 element date
- this version of the application profile adopts the Date element in combination with dateType attribute from DataCite MetadataKernel v4.1.
10.2.1. Property date (M, 1)¶
Use the publication date as value.