<event>
Event in Publishing History
An event in the publication history of an article, for example,
reprinting or publishing a revised online edition. This element may contain information such as a description of the event (<event-desc>), copyright information for a reprint or edition, a publication date, a URI for the article, etc.
Remarks
An <event> can be the description of a pre- or post-publication event including dates, link(s), an article version, and/or descriptive commentary. An <event> element can also be used to describe earlier versions of an article. As an example, one publisher has an article that was posted on a preprint server, then one version of the author’s accepted manuscript was published, then a subsequent version revising this document was published, then the version of record was published, and then an updated version of record was published. No official “corrections” were published with any of these documents, but each new document can be described with an <event> element.
Attributes
Content Model
<!ELEMENT event %event-model; >
Expanded Content Model
(event-desc?, article-id*, (article-version | article-version-alternatives)?, ((pub-date)* | pub-date-not-available?), (date | string-date)*, issn*, issn-l?, isbn*, permissions?, notes*, self-uri*)
Description
The following, in order:
- <event-desc> Event Description, zero or one
- <article-id> Article Identifier, zero or more
- Optionally any one of:
- Any one of:
- <pub-date> Publication Date, zero or more
- <pub-date-not-available> Publication Date Not Available Flag, zero or one
- Any combination of:
- <issn> ISSN, zero or more
- <issn-l> ISSN-L (Linking ISSN), zero or one
- <isbn> ISBN, zero or more
- <permissions> Permissions, zero or one
- <notes> Notes, zero or more
- <self-uri> URI for This Same Article Online, zero or more
This element may be contained in:
Example 1
... <article-meta> ... <pub-history> <event event-type="received"> <event-desc>Received: <string-date iso-8601-date="2017-09-12"> <month>September</month> <day>12</day>, <year>2017</year></string-date></event-desc> </event> <event event-type="accepted"> <event-desc>Accepted: <string-date iso-8601-date="2018-05-26"> <month>May</month> <day>26</day>, <year>2018</year></string-date></event-desc> </event> <event event-type="pub"> <event-desc>Accepted Manuscript published: <string-date iso-8601-date="2018-05-30"> <month>May</month> <day>30</day>, <year>2018</year></string-date> (version 1)</event-desc> </event> <event event-type="pub"> <event-desc>Version of Record published: <string-date iso-8601-date="2018-06-13"> <month>June</month> <day>13</day>, <year>2018</year></string-date> (version 2)</event-desc> </event> </pub-history> </article-meta>...
Example 2
A more detailed event description:
...
<article-meta>
...
<pub-history>
<event event-type="revision">
<event-desc>The first version of this article was
enhanced considerably between versions of the XML
instance. These changes can be seen <ext-link
ext-link-type="uri"
xlink:href="https://elifesciences.org/content/5/e00666v3">
here</ext-link>.</event-desc>
<date date-type="accepted-manuscript-r1"
iso-8601-date="2016-07-29">
<day>29</day><month>07</month>
<year>2016</year>
</date>
<self-uri content-type="accepted-manuscript"
xlink:href="https://elifesciences.org/content/5/e00666v2"/>
</event>
...
</pub-history>
</article-meta>
...