[jats-list] Re: [JATS-List:] Preprint DOI handling

["Owens, Evan evan.owens@xxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Hi Caroline,

At the Crossref annual meeting last November the session on DOIs for Preprints
said that this was about allowing preprint sites to register a DOI separately
from the publisher's DOI for the published article and then how to track the
relationship between the two DOIs in Crossref metadata.    In the past
preprints were not allowed to be registered with Crossref.

Is this customer question actually about preprint services (something
completely separate from journal publication)?  Is the customer posting all
submissions as preprints, separate from what is accepted?   Or is about the
publisher posting the accepted manuscript and calling it a "preprint"?  If the
publishers is posting the accepted manuscript then replacing it with the
published version of record, that would not require separate DOI.   Would the
version that this customer is posting still be online after the published
article is online?

The other new Crossref feature coming soon is to allow publishers to register
the DOI at acceptance and before publishing (making it available online); that
is entirely new functionality.  This was described as to support having DOIs
in press releases announcing an article before publication and to support
tracking funding info at acceptance rather than at publication.

Evan Owens
VP Publishing Technologies, Cenveo Publisher Services
2905 Byrdhill Road, Richmond VA 23228
Office: (804) 515-5146   Mobile: (804) 380-3350




From: Caroline Webber cwebber@xxxxxxxxxxxx
[mailto:jats-list-service@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, February 18, 2016 10:25 AM
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
Cc: Caroline Webber
Subject: [jats-list] [JATS-List:] Preprint DOI handling

Hi all,

How should preprint DOI's be tagged in the JATS? We have a customer who is
going to start posting preprints early in the process, and our understanding
is that CrossRef is now (or soon) requiring a separate "preprint DOI".

I had a thought tagging it like this: <article-id
pub-id-type="preprint-doi">.

However, I discussed this with Bruce, and he had an alternate suggestion:

For the transmittal of the preprint article, use <article-id
pub-id-type="doi">, and then for the transmittal of the final article related
to the preprint, tag the preprint as a <related-article>. However, he pointed
out that there are currently no attributes for related-article-type that fit
the bill (currently the related-article-type values are suggested as
"addendum", "commentary", "commentary-article", "companion", etc).  Should we
consider adding "preprint" to the list of suggested attribute values?

Caroline Webber l Senior Business Systems Analyst

Aries Systems Corporation l www.ariessys.com<http://www.ariessys.com/>
200 Sutton Street l North Andover, MA l 01845 l USA
Direct: 978-291-1941 l Main: 978-975-7570 l Fax: 978-975-3811

For the latest EM, PM, and industry news, subscribe to our e-newsletter and
view archived issues
here<http://www.ariessys.com/views-and-press/newsletter-archive/>!

[cid:image001.png@xxxxxxxxxxxxxxxxx]<http://www.ariessys.com/views-and-press/
resources/video-library/>     [cid:image002.png@xxxxxxxxxxxxxxxxx]
<http://www.ariessys.com/>

[cid:image003.png@xxxxxxxxxxxxxxxxx]<https://twitter.com/ariesmarketing>[cid:
image004.png@xxxxxxxxxxxxxxxxx]<https://www.facebook.com/editorialmanager/>
[cid:image005.png@xxxxxxxxxxxxxxxxx]
<https://www.linkedin.com/company/aries-systems-corporation>

This message is confidential and is intended solely for the use of the
individual(s) to whom it is addressed.
If you have received this message in error, do not open any attachment but
please notify the sender (above) and delete this message from your system.


****
JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/>
EasyUnsubscribe<-list/2589070> (by email<>)

****

[demime 1.01d removed an attachment of type image/png which had a name of image001.png]

[demime 1.01d removed an attachment of type image/png which had a name of image002.png]

[demime 1.01d removed an attachment of type image/png which had a name of image003.png]

[demime 1.01d removed an attachment of type image/png which had a name of image004.png]

[demime 1.01d removed an attachment of type image/png which had a name of image005.png]