<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.

Related Elements

An <event> provides a more complete description of a date in the lifecycle of an article than can be provided by merely putting a <date> element inside <history>.
Role of <date>: Inside both <history> and <event>, the <date> element can identify the type of date using the attribute @date-type (“received”, “accepted”) and the format of the publication using the @publication-format attribute (“print”, “electronic”).
Role of <event>: In addition to one or more dates, the <event> inside <pub-history> can provide:
  • A human readable description of the publishing event,
  • article version and article identification numbers,
  • the publication date associated with the event,
  • and ISSN or linking ISSN,
  • copyright and licensing information,
  • one or more URIs, and
  • additional notes.
Best Practice: An <event> may include those things that are usually handled by <history>, such as when the manuscript was received or accepted, but an <event> need not be recorded for any particular date in history. However, the JATS Standing Committee recommends that, within a single XML document, either the <history> or the <pub-history> element be used. In other words, if some of your significant dates need to be described as events, all your dates should be inside <event> in <pub-history> and the any existing <date> elements within <history> made into pub-history/event dates.

Attributes

event-type Type of Event
id Document Internal Identifier
specific-use Specific Use
xml:base Base
xml:lang Language

Content Model

<!ELEMENT  event        %event-model;                                >

Expanded Content Model

(event-desc?, article-id*, (article-version | article-version-alternatives)?, pub-date*, (date)*, issn*, issn-l?, isbn*, permissions?, notes*, self-uri*)

Description

The following, in order:

This element may be contained in:

<pub-history>

Example 

...
<article-meta>
...
<pub-history>
<event>
 <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>
...

Journal Publishing Tag Library NISO JATS Version 1.2d1 (ANSI/NISO Z39.96-2015)

Version of July 2017

Back to Top