texture
texture copied to clipboard
substance
Email address
Description
An email address associated with an author.
User stories
Author
- (1) As an author, I want to be able to see an email address associated with an author so that I can make sure this information is correct in the published article.
Production staff
- (2) As production staff, I want to be able to edit an email address associated with an author so that I can correct this information if requested.
- (3) As production staff, I want to be able to remove an email address to an author so that I can delete incorrect information.
- (4) As production staff, I want to be able to add an email address to an author so that I can add missing information.
But what if . . . ?
Consideration
- eLife requires these for corresponding authors, but requires that they are not present for non-corresponding authors. This consideration will be different for other publishers (corresponding status covered in ticket https://github.com/elifesciences/TextureRequirements/issues/11).
- For Érudit, one or more authors can have an email address and all the e-mails are displayed in the website: https://www.erudit.org/fr/revues/cgq/2010-v54-n152-cgq4005/045646ar/ (at the moment, all authors will an email address will be treated as @corresp="yes").
- Currently, eLife allows group authors to have multiple email addresses associated with them (see #54)
XML requirements
Captured using the email element, as a child of the appropriate contrib element.
<contrib corresp="yes">
<name>
<surname>Harrison</surname>
<given-names>Melissa</given-names>
</name>
<email>[email protected]</email>
...
</contrib>
<contrib corresp="yes">
<collab>eLife Production Group</collab>
<email>[email protected]</email>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname>Atherden</surname>
<given-names>Fred P</given-names>
</name>
</contrib>
...
</contrib-group>
</contrib>
Group authors may have more than one email address:
<contrib corresp="yes">
<collab>Reproducibility Project: Cancer Biology</collab>
<email>[email protected]</email>
<email>[email protected]</email>
<contrib-group>
<contrib>
<name>
<surname>Errington</surname>
<given-names>Tim</given-names>
</name>
</contrib>
<contrib>
<name>
<surname>Pfeiffer</surname>
<given-names>Nicole</given-names>
</name>
</contrib>
…
</contrib-group>
</contrib>
Mock ups
Proposal
Could we assume that when an email is provided, that the author is a corresponding author and save that in the XML, but only capture "email" or "not email" in the editor?
Could we assume that when an email is provided, that the author is a corresponding author and save that in the XML, but only capture "email" or "not email" in the editor?
This would not work for another journal we are working with for Libero so I think it would not be a good idea to set it up this way. Sorry!
Could we assume that when an email is provided, that the author is a corresponding author and save that in the XML, but only capture "email" or "not email" in the editor?
Could you elaborate on this?
Having an email and being corresponding author is not necessary the same IMO. What is the reasoning behind this?
Note: I personally try to avoid any implicit mechanism. I.e. if 'corresponding author' is a concept, i would prefer an explicit representation in the model.
Having an email and being corresponding author is not necessary the same IMO. What is the reasoning behind this?
The corresponding author is the person readers should contact if they want to ask the authors something about the paper. The other authors may display their email address, but they are not the official contact for the actual paper. Does that make sense?
I agree, not great.
Understand, let's capture this in two separate fields then. My assumption was based on Erudit's use-case. But makes perfect sense to have emails for a number of authors where only some of them are corresponding authors. Updated the proposal as well to reflect this. See #1269.