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

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

Hi Bruce,

Thanks for the follow up information from Ed Pentz and clarification on this
issue.  Not mentioned at the Crossref annual meeting session.   So this is
about the content distinction between pre-publication and publication rather
than just about linking from pre-print sites to publisher sites.   A good
enhancement to the citation process.   And more revenue for Crossref.

In the early CHORUS discussions about publishers posting the accepted
manuscript for public access and having both AM and VOR on their websites,
Geoff Bilder of Crossref proposed that those be separate DOIs.  Publishers
weren't keen on that because they were using a single landing page for each
article with links to the different versions based on accessibility status
(e.g., subscribes got access to VOR and public got access to AM).   And it
wasn't obvious how to register this with Crossref then.  But sounds like it
now would be possible.

Evan

From: Bruce Rosenblum bruce@xxxxxxxxx
[mailto:jats-list-service@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, February 18, 2016 11:18 AM
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx; jats-list@xxxxxxxxxxxxxxxxxxxxxx
Cc: Caroline Webber
Subject: Re: [jats-list] Re: [JATS-List:] Preprint DOI handling

Hi Evan,

I had an email exchange with Ed Pentz about this two weeks ago. The new
CrossRef policy (and I quote from his email) is:

"Crossref's policy is that the version of record should definitely have a
separate DOI from the working paper/preprint form. As you say, the working
paper form will have been cited and anyone following the citation should go to
what was cited. Of course, the working paper should make it clear that there
is a version of record/new version and have a prominent link to it. The
working paper/preprint and version of record are two different citable items
whether [the same publisher] publishes both or they are published by different
publishers. If they have the same DOI it messes up the citation record"

The bold is my addition.

Just to be clear, the context of my original question to Ed was whether there
should be a new DOI even if the version of record is then published by the
same publisher who publishes the pre-print. I thought that case might be
different, but Ed's answer was that it is not different and there should still
be two DOIs

It was in the context of this new policy that I provided the guidance to
Caroline, i.e. separate DOIs for the pre-print and final, and use
related-article to reference the pre-print from the final. In this context,
then the only question is what's the appropriate attribute value for
related-article-type

Bruce

At 11:05 AM 2/18/2016, Owens, Evan
evan.owens@xxxxxxxxxx<mailto:evan.owens@xxxxxxxxxx> wrote:

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\x92s 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 \x93preprint\x94?
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:cwebber@xxxxxxxxxxxx> [
mailto:jats-list-service@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, February 18, 2016 10:25 AM
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx<mailto:jats-list@xxxxxxxxxxxxxxxxxxxxxx>
Cc: Caroline Webber
Subject: [jats-list] [JATS-List:] Preprint DOI handling

Hi all,

How should preprint DOI\x92s 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 \x93preprint DOI\x94.

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
\x93addendum\x94, \x93commentary\x94, \x93commentary-article\x94,
\x93companion\x94, etc).  Should we consider adding \x93preprint\x94 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.htm> (by email)

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

-------------------------------------------------------------------
This email message and any attachments are confidential. If you are not the
intended recipient, please immediately reply to the sender or call
617-932-1932 and delete the message from your email system. Thank you.
-------------------------------------------------------------------
Bruce D. Rosenblum
Inera Inc.
19 Flett Road, Belmont, MA 02478
phone: 617-932-1932 (office)
email: bruce@xxxxxxxxx<mailto:bruce@xxxxxxxxx>
web: www.inera.com<http://www.inera.com/> | www.edifix.com
<http://www.edifix.com/>twitter:  @eXtyles | @edifix
****
JATS-List info and archive<http://www.mulberrytech.com/JATS/JATS-List/>
EasyUnsubscribe<-list/2589070> (by email<>)

****