search

substance / texture

A visual editor for research.
MIT License
1k stars 83 forks source link

Email address #1260

Open JGilbert-eLife opened 5 years ago

JGilbert-eLife commented 5 years ago

Description

An email address associated with an author.

User stories

Author

Production staff

But what if . . . ?

Consideration

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>m.harrison@elifesciences.org</email>
       ...
</contrib>
<contrib corresp="yes">
       <collab>eLife Production Group</collab>
       <email>f.atherden@elifesciences.org</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>tim@cos.io</email>
      <email>nicole@scienceexchange.com</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

michael commented 5 years ago

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?

fabiobatalha commented 5 years ago

@michael

Yes for Érudit.

Melissa37 commented 5 years ago

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!

obuchtala commented 5 years ago

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.

Melissa37 commented 5 years ago

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.

obuchtala commented 5 years ago

Does that make sense?

Yes.

michael commented 5 years ago

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.