Container element for dates related to the processing history of the document (for example, received date, accepted date).
Best Practice: The dates inside the <history> element are used to 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>. History dates 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 <history> element contains one more <date> and/or <string-date> elements; the <date> element has specific parts, such as day and year, inside it and the <string-date> has a textual description of a date. Best practice for the <history> element is to use to use <date> as much as possible and tag the date components. The <string-date> element should be used only when necessary, for example, when the date does not divide into year and month components. If an archive chooses to make greater use of <string-date>, for example, to save money during conversion, it is still considered best practice to tag the year of publication inside the textual date using a <year> element.
The Archiving and Interchange Tag Set allows <string-date> both inside date and at the same level as date. This is the most flexible for allowing the archive to preserve any publisher’s structure. The tighter Tag Sets created from the base Suite may choose to use one or the other in preference.
<!ELEMENT history %history-model; >
(#PCDATA | email | ext-link | uri | inline-supplementary-material | related-article | related-object | hr | bold | fixed-case | italic | monospace | overline | overline-start | overline-end | roman | sans-serif | sc | strike | underline | underline-start | underline-end | ruby | alternatives | inline-graphic | private-char | chem-struct | inline-formula | tex-math | mml:math | abbrev | milestone-end | milestone-start | named-content | styled-content | fn | target | xref | sub | sup | x | break | date | string-date)*
Any combination of:
In article metadata, an approval date:
... <article-meta> ... <contrib-group> <contrib contrib-type="author"> <collab collab-type="committee">Technical Committee ISO/TC 108, Subcommittee SC 2</collab> </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> ...
In article metadata, several 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-received" 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> ...
This history contains character data rather than tagged dates:
... <article-meta> ... <supplementary-material>...</supplementary-material> <history>Paper submitted August 22, 2000; pending government agency review/approval, revised manuscript accepted June 12, 2002.</history> <permissions> <copyright-statement>...</copyright-statement> </permissions> ... </article-meta> ...