Article Event Lifecycle

  1. The <pub-history> element is a container for recording of the processing history of the article. It can include received/revised/accepted/retracted dates, but also additional events such as reprint or different versions published (in <event> element).

  2. <event> inside <pub-history> in an event in the processing history of the article and can include date <date> as well as event description <event-desc>.

  3. <tf:tagger> from TF JATS has been replaced with @event-type="tagger”. “Tagger” identifies who created or updated an XML and it should be set to the name of the typesetter, organization, or individual (i.e., EPU) or converter script. <event event-type="tagger"> needs to be stripped out in the 3rd-party feeds.

  4. The <date> format is as follows:

    <day>D</day><month>M</month><year>YYYY</year> and no longer iso-8601-date="2019-05-01”.

Each <event> element must have an @event-type attribute that identifies the event using a value from the following list.

event-type description
tagger name of typesetter/prepress vendor or publisher that typeset the article or created the XML
xml-created XML created after the initial typesetting (XML last)
xml-converted XML converted to JATS 1.2 from existing XML source
digitized XML created from PDF or scanned physical materials
provenance XML tagging amendment by Digital Production
received manuscript was received or submitted for peer review
revised manuscript was revised during peer review
accepted manuscript was accepted for publication
accepted-manuscript published online as an accepted manuscript
ahead-of-issue published online ahead of issue
build-issue-online published online in a building issue
final published online as a final version in an issue
corrected article corrected following correction policy
retracted article retracted

Examples

Peer review received, revised, and accepted dates:

<pub-history>
<event event-type="received"><date><day>1</day><month>5</month><year>2019</year></date></event>
<event event-type="revised"><date><day>19</day><month>5</month><year>2019</year></date></event>
<event event-type="accepted"><date><day>1</day><month>6</month><year>2019</year></date></event>
</pub-history>

Typesetter / Prepress Vendor for current content:

<pub-history>
<event event-type="tagger">
<event-desc>Perfect Typesetting</event-desc>
<date><day>12</day><month>9</month><year>2019</year></date>
</event>
</pub-history>

Retrodigitization XML Conversion for converted content:

<pub-history>
<event event-type="tagger">
<event-desc>XYZ Press</event-desc>
</event>
<event event-type="xml-converted">
<event-desc>Received from XYZ in NLM 2.2 format and converted to JATS 1.2 by Perfect Typesetting</event-desc>
<date><day>12</day><month>9</month><year>2019</year></date>
</event>
</pub-history>

Retrodigitization scanning from hardcopy for scanned content:

<pub-history>
<event event-type="tagger">
<event-desc>XYZ Press</event-desc>
</event>
<event event-type="digitized">
<event-desc>Perfect Typesetting</event-desc>
<date><day>12</day><month>9</month><year>2019</year></date>
</event>
</pub-history>

Typesetter / Prepress Vendor followed by XML creation for current content:

<pub-history>
<event event-type="tagger">
<event-desc>Chris Designer</event-desc>
<date><day>12</day><month>9</month><year>2019</year></date>
</event>
<event event-type="xml-created">
<event-desc>Converted from InDesign to JATS 1.2 by Perfect Typesetting</event-desc>
<date><day>12</day><month>9</month><year>2019</year></date>
</event>
</pub-history>