Home | Public Area

Comment #00663 - Storing extended publication events in the XML - z39_96-2015.pdf (revision #1)

Comment 663
Addressed (Unresolved)
ANSI/NISO Z39.96-2015, JATS: Journal Article Tag Suite, version 1.1 (Revision 1)
Comment Submitted by
Melissa Harrison
2016-10-14 06:39:04

Problem:



At eLife and BMJ, we want to store information about publication events in the XML. These could be pre- or post-publication events that would include date, link(s),  and descriptive commentary.



 



Events may include those things that are usually handled by <history> such as when the manuscript was received or accepted. But they may also be details of earlier versions of the article. For example, eLife have articles that have been posted on a preprint server, published one version of an author?s accepted manuscript, a subsequent version of this format, a version of record and then another updated version of record. There are no official corrections published with these event changes. We need to be able to store date, identifier and/or link information for the other versions, and comments on the changes.



 



<self-uri> and the current <history> models each solve only one part of the problem. 

Submitter Proposed Solution

The best solution we see is the <event> element from the BITS <pub-history>



Please allow <event> and associated attributes from the BITS DTD into the JATS DTD (Blue and Green) within <history> so eLife and BMJ could tag the following (2 examples provided):



 



<history>?



<event>



<self-uri content-type="accepted-manuscript-r1? xlink:href="https://elifesciences.org/content/5/e00666v2"/>



<date date-type="accepted-manuscript-r1" iso-8601-date="2016-07-27">

<day>27</day>

<month>07</month>

<year>2016</year>

</date>



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

</ event >





 



<history>



    <event>



        <self-uri xlink:href="http:/journala.puba.com/preprints/abcd12390" content-type="preprint"/>



        <date date-type="submitted" iso-8601-date="2001-01-29">



            <day>29</day>



            <month>01</month>



            <year>2001</year>



        </date>



        <date date-type="rejected" iso-8601-date="2001-02-15">



            <day>15</day>



            <month>02</month>



            <year>2001</year>



        </date>



        <event-desc>The first version of this work was submitted to Journal A and rejected because "the subject matter is outside the editorial scope of the journal"</event-desc>



    </event >



    <event>



        <self-uri xlink:href="http:/journalB.pubB.com/preprint/abrft6789" content-type="preprint">



            <date date-type="submitted" iso-8601-date="2001-03-03">



                <day>03</day>



                <month>03</month>



                <year>2001</year>



            </date>



            <date date-type="accepted" iso-8601-date="2001-02-15">



                <day>15</day>



                <month>02</month>



                <year>2001</year>



            </date>



            <event-desc>A slightly reworked manuscript of this article was accepted at Journal B</event-desc>



        </event>



        <event>



            <self-uri xlink:href="http:/journalB.pubB.com/content/45/journb.a788889" content-type="VoR"/>



            <date date-type="epub" iso-8601-date="2001-06-06">



                <day>06</day>



                <month>06</month>



                <year>2001</year>



            </date>



            <event-desc>Extra figures and a table reworked for clarity after editorial review. Final version published in Journal B</event-desc>



        </event>



    </history>



 

Ms. B. Tommie Usdin
2017-08-31 08:36:50

We will add an <event> element, similar to the one in BITS, to the JATS models.