<date> Date

Container element for the parts of a single calendar date.

Usage/Remarks

A <date> element contains date components such as <day>, <month>, and <year> (which are typically given numeric values), as well as non-numeric elements such as <season> (which is a text string).
<date>In Citations, Related Articles, and Products
When used within citations (<element-citation> and <mixed-citation>), related articles and objects, and product descriptions, <date> names the publication date of the cited or related source.
<date>In Events and History
When used as part of <event> or <history>, this element holds one of the publication history dates that may be preserved for an article, such as when it was received or when it was accepted.

Best Practice: Use @iso-8601-date

It is recommended to provide an @iso-8601-date attribute on every <date> element, for better machine processing and interoperability

Best Practice: Use <event> Rather Than <history>

Current publishing best practice is not to use the element <history> and instead, tag all publishing dates as <event>s.
  • For retrospective conversion, each <date> element inside <history> can be moved into <event> without change and without addition.
  • Going forward, the <event> structure allows the publisher to record additional metadata beyond the bare type values (“accepted”, “preprint”, “rejected”, etc.) that are recorded in the @date-type attribute.

<string-date> Best Practice

In <date>, individual date elements (such as <year>) must be tagged. However, even inside a <string-date>, the named date components such as <year> should be identified. Use <string-date> for the narrative form of a date when necessary, for example, when a date has no month or year specified or to change the order of date elements.
Related Elements
Within citations (<element-citation> and <mixed-citation>), this element names a date, typically the publication date of the cited source. The elements <year>, <date>, <day>, <month>, and <season> may all be used to describe a date in a citation, both publication dates and other dates. Other dates inside a citation, such as a copyright date, the date on which the author accessed the resource, or a withdrawal date, should be tagged using <date-in-citation> with the @content-type attribute used to name the type of date (copyright, access-date, time-stamp, etc.).
Attributes

Base Attributes

Models and Context
May be contained in
Description
The following, in order:
Content Model
<!ELEMENT  date         %date-model;                                 >
Expanded Content Model

(((day?, month?) | season)?, year, era?)

Tagged Samples
Event: Date accepted
...
<article-meta>
 ...
<pub-history>
  <event><event-desc>Accepted for publication</event-desc>
   <date date-type="accepted" iso-8601-date="2012-06-01">
     <day>01</day>
     <month>06</month>
     <year>2012</year>
   </date>
  </event>
</pub-history>
 ...
</article-meta>
...
Non-Gregorian calendar
...
<date date-type="received" calendar="Japanese" 
  iso-8601-date="2013-07-01">
 <day>1</day>
 <month>7</month>
 <year>25</year>
 <era>平成</era>
</date>
...
Publication date in citations
Mixed citation
...
<ref id="B14">
 <mixed-citation publication-type="book" publication-format="print">
  <person-group person-group-type="author">
  <name><surname>Hart</surname><given-names>JT</given-names>
  </name></person-group>. <source>A new kind of doctor: the 
  general practitioner&rsquo;s part in the health of the 
  community</source>. <publisher-loc>London</publisher-loc>:  
  <publisher-name>Merlin Press</publisher-name>, 
  <date iso-8601-date="1988" date-type="pub"><year>1988</year></date>.
 </mixed-citation>
</ref>
...
Element citation
...
<ref id="B14">
 <element-citation publication-type="book" publication-format="print">
  <person-group person-group-type="author">
   <name><surname>Hart</surname>
    <given-names>JT</given-names></name>
  </person-group>
  <source>A new kind of doctor: the general practitioner&rsquo;s 
   part in the health of the community</source>
  <date iso-8601-date="1988" date-type="pub">
   <year>1988</year>
  </date>
  <publisher-loc>London</publisher-loc>
  <publisher-name>Merlin Press</publisher-name>
 </element-citation>
</ref>
...
Related Resource
https://jats.nlm.nih.gov/publishing/tag-library/1.4d1/element/date.html
jats.nlm.nih.gov
CC-MAIN-2024-38
399450
application/http; msgtype=response
sha1:4CW63MTFRKBL7RUNVTGS5V3VFLLNH7NB
<urn:uuid:1ebd93d4-fbe4-4556-b042-aa0568486b3d>
2024-09-17T02:35:36Z
130.14.29.110
text/html
sha1:QBT3AHNVRAXF4JHO4EOGL3O3MLAP2PAS
<urn:uuid:528754a4-0f2d-4409-ad0a-456e9cf1fc0b>
https://jats.nlm.nih.gov/publishing/tag-library/1.4d1/element/date.html
response
<urn:uuid:0c7d3f8b-5717-49d0-a013-2895afcdd01f>
isPartOf: CC-MAIN-2024-38
publisher: Common Crawl
description: Wide crawl of the web for September 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-225
software: Apache Nutch 1.20 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/