◇◆

<history> History: Document History (deprecated)

Container element for dates related to the processing history of the document (for example, received date, accepted date). This element is deprecated.

Usage/Remarks

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

Current publishing Best Practice is not to use the element <history>, which has been deprecated, but instead, tag all publishing dates as <event>s.
  • For retrospective conversion, each <date> element inside <history> can be moved as a date element 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.
Dates within <event> <history>
Publication Dates — The date described inside the <event> element (as well as inside the deprecated <history>) preserve events other than publication date(s) in the life cycle of the article. Publication dates are considered to be an important part of the article metadata and are tagged using the <pub-date> element inside the element <article-meta>.
Other Lifecycle Dates — In both <event> and in the deprecated <history>, lifecycle dates (tagged with <date>) can include received date(s), accepted date(s), reviewed date(s), revision date(s), and other dates that may be important to the publisher, but are not a likely part of the metadata concerning the article that is used for searching, building a DOI, etc. The <event> element, unlike <history> also contains metadata about the date being recorded, including descriptions, permissions, and notes.
Current Best Practice is to tag these lifecycle dates inside <event> elements, adding other metadata so that these recorded dates are not merely <date> elements.
Attributes

Base Attributes

id
xml:base
Models and Context
May be contained in
<article-meta>, <front-stub>
Description
<date> Date, one or more
Content Model
<!ELEMENT  history      %history-model;                              >
Expanded Content Model

(date)+

Tagged Samples
Approval date 
...
<article-meta>
 ...
 <contrib-group>
  <contrib contrib-type="author">
   <collab-name collab-type="committee">Technical Committee ISO/TC 108, 
    Subcommittee SC 2</collab-name>
  </contrib>
 </contrib-group>
 ...
 <fpage seq="1">1</fpage>
 <lpage>23</lpage>
 <history>
  <date date-type="approved" iso-8601-date="2012-06-01">
   <day>01</day>
   <month>06</month>
   <year>2012</year>
  </date>
 </history>
 ...
</article-meta>
...
Various lifecycle dates 
...
<article-meta>
 ...
 <pub-date publication-format="electronic" date-type="pub" iso-8601-date="1998-09-17">
  <day>17</day>
  <month>09</month>
  <year>1998</year>
 </pub-date>
 <pub-date publication-format="print" date-type="pub" iso-8601-date="1998-11-09">
  <day>09</day>
  <month>11</month>
  <year>1998</year>
 </pub-date>
 <volume>31</volume>
 <issue>187</issue>
 <fpage>483</fpage>
 <lpage>501</lpage>
 <history>
  <date date-type="received" iso-8601-date="1998-01-05">
   <day>05</day>
   <month>01</month>
   <year>1998</year>
  </date>
  <date date-type="rev-request" iso-8601-date="1998-03-14">
   <day>14</day>
   <month>03</month>
   <year>1998</year>
  </date>
  <date date-type="rev-recd" iso-8601-date="1998-05-24">
   <day>24</day>
   <month>05</month>
   <year>1998</year>
  </date>
  <date date-type="accepted" iso-8601-date="1998-06-06">
   <day>06</day>
   <month>06</month>
   <year>1998</year>
  </date>
 </history>
 ...
</article-meta>
...
Related Resources