Re: [jats-list] Primary Corresponding author

["Pieter Lamers pieter.lamers@xxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Hi Rob,

Our solution is to explain to authors that corresponding lo longer means
corresponding, but is in active use as a referral for R&P, and that
there can only be one 'corresponding' author as a consequence. However,
it is semantically awful. I do not like using 'specific-use' here as it
suggests something else than what is going on.

Best
Pieter

On 13/05/2021 17:12, Robert O'Donnell odonner@xxxxxxxxxxxxxxx wrote:
> Thanks, all. Tommie b I will add the suggestion. I think that this hasn't
come up before because there haven't been use cases, but with Read & Publish,
that has changed.
> Nikos b I like the idea of <xref rid="..." ref-type="corresp"
specific-use="primary">. It just needs to somewhat if a standard practice so
that any organization using the XML knows what to look for. Perhaps this can
be incorporated into the JATS4R Authors and affiliations recommendation. I'm
going to suggest that.
> Pieter b I'm glad to hear that you too have been thinking about this.
While I agree that "primary author" could work, I think deals and
universities, as you mention, have adopted the term corresponding. I'd be
reluctant to try to change what is already in use and already in signed
agreements. I'd also be slightly concerned that authors could be
confused/upset that "primary" might be perceived as more important than senior
author.
> Thanks,
>
> Rob
>
>
>
> Rob O'Donnell
>
> Director of Publishing Technologies
>
> +1.212.327.8545
>
> Rockefeller University Press
>
> 950 Third Avenue, Floor 2, New York, NY 10022
>
> rupress.org | jcb.org | jem.org | jgp.org | lsajounral.org
>
>
>
> From: Pieter Lamers <pieter.lamers@xxxxxxxxxxxx>
>
> Sent: Wednesday, May 12, 2021 3:44 PM
>
> To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
>
> Subject: Re: [jats-list] Primary Corresponding author
>
>
>
> We recently had an internal discussion about the topic of having multiple
corresponding authors. We are seeing that universities want to have a single
primary author, but have adopted the term corresponding for that. The need for
a single primary author is for instance for the so-called Read & publish deals
between a university and a publisher, where a university pays a sum based on
some previous count of articles of which the corresponding author was
affiliated with them. Having just one author means that there will not be a
double count of articles with multiple authors from different universities. In
return all current publications with the same criterion (within a certain
timeframe) will be made Open Access without any further billing per article.
In this day and age, the actual (email) correspondence can be with any number
of authors on cc. It would be nicer if we could use an attribute primary
instead of corresp for the intended statistics. I imagine a similar situation
is relevant for TS. It would be useful to have a proper identification for
primary as authors may take pride in being the first, primary, corresponding
one, and if it is not crystal clear to them that there can be only one, we
might end up having the same situation with primary as we were having with
corresponding.
> Best
>
> Pieter
>
> On 12/05/2021 15:54, Nikos Markantonatos mailto:nikos@xxxxxxxxxx wrote:
>
> Hello.
>
>
>
> Is this information that you wish to maintain per contributor? Have you
considered <xref rid="..." ref-type="corresp" specific-use="primary">?
> If it does not have to be per contributor, then one idea would be: <corresp
content-type="primary"> for the primary correspondence statement.
> Nikos
>
>
>
> On 5/12/21 4:38 PM, Robert O'Donnell mailto:odonner@xxxxxxxxxxxxxxx wrote:
>
> Hi - Any suggestions on tagging a *primary* corresponding author (CA)? We
identify primary CAs in our submission and production systems, and use that
info for many purposes, including read & publish deal billing, proof delivery,
etc. In the final version of an article, we allow multiple authors to be
tagged for correspondence using @corresp="yes". Of course, this makes it
impossible to identify the *primary* corresponding author. As read & publish
deal eligibility based on the primary corresponding author's affiliation grows
in use, reporting via JATS on platforms like the OA Switchboard becomes
increasingly inaccurate. Same goes for JATS XML ingested by Dimensions,
CHORUS, etc. So it's becoming increasingly important to distinguish the
primary CA. We also need for Crossref to start identifying CAs in general, and
hopefully when they do, if primary CAs are tagged distinctly in JATS, Crossref
metadata will reflect this.
> Thoughts and suggestions? Is such an enhancement already in the works?
>
>
>
> Thanks,
>
> Rob
>
>
>
> Rob O'Donnell
>
> Director of Publishing Technologies
>
> +1.212.327.8545
>
> Rockefeller University Press
>
> 950 Third Avenue, Floor 2, New York, NY 10022
>
> rupress.org | jcb.org | jem.org | jgp.org | lsajounral.org
--
Pieter Lamers
John Benjamins Publishing Company
Postal Address: P.O. Box 36224, 1020 ME AMSTERDAM, The Netherlands
Visiting Address: Klaprozenweg 75G, 1033 NN AMSTERDAM, The Netherlands
Warehouse: Kelvinstraat 11-13, 1446 TK PURMEREND, The Netherlands
tel: +31 20 630 4747
web: www.benjamins.com