Non-author contributor roles

Designates the kind of non-author contributor e.g. reviewer, reviewing editor, senior editor, translator etc.

User Stories

Author

As an author, I want to be able to see the role assigned to each non-author contributor so that I can check that this information is correct.

Production staff

As production staff, I want to be able to edit the role for a non-author contributor so that I can correct any errors.
As production staff, I want to be able to assign a role to a non-author contributor from a preset list of options so that I can include this information easily.
As production staff, I want to be able to add a custom role to a non-author contributor so that I can assign a piece of non-standard information that is not available as a preset option.

But what if . . . ?

Considerations

eLife only allows the following values for <role>:
- Reviewer
- Senior Editor
- Reviewing Editor
Érudit allows e.g. Translator.
The same person can be both senior and reviewing editor, and at the moment eLife would list that person twice. However, we would prefer simply to add multiple roles per person.
In eLife articles, there should only be one Reviewing Editor and one Senior Editor per article; however, not every article will have editors listed (see #47).

XML requirements

Roles are identified using the role element.

<contrib-group content-type="peer-review">
      <contrib>
            <name>
                  <surname>...</surname>
                  <given-names>...</given-names>
             </name>
            <role>Reviewing Editor</role>
            <xref ref-type="aff" rid="aff5">5</xref>
      </contrib>
      <contrib>
            <name>
                  <surname>...</surname>
                  <given-names>....</given-names>
            </name>
            <role>Senior Editor</role>
            <xref ref-type="aff" rid="aff5">5</xref>
      </contrib>
      <contrib>
            <name>
                  <surname>...</surname>
                  <given-names>....</given-names>
            </name>
            <role>Reviewer</role>
            <xref ref-type="aff" rid="aff6">6</xref>
      </contrib>
      <aff id="aff5"><institution>...</institution><country>...</country></aff>
      <aff id="aff6"><institution>...</institution><country>...</country></aff>
</contrib-group>
<contrib-group content-type="translators">
    <contrib>
                    <name>
                        <surname>...</surname>
                        <given-names>....</given-names>
                    </name>
                    <role>French Translator</role>
                    <xref ref-type="aff" rid="aff7">7</xref>
    </contrib>
    <aff id="aff7">
        <institution>...</institution>
        <country>...</country>
         </aff>
</contrib-group>

A contributor may have more than one role:

<contrib-group content-type="peer-review">
      <contrib>
            <name>
                  <surname>Bright</surname>
                  <given-names>John</given-names>
            </name>
            <role>Reviewing Editor</role>
            <role>Senior Editor</role>
            <xref ref-type="aff" rid="aff5">5</xref>
      </contrib>
      ...
</contrib-group>

Custom Vocabulary

Texture needs to allow for customisable role values. There should be a certain set of 'allowed' role values, which a publisher can add to or remove from in their configuration. This will allow for various customisable roles to be accounted for without the need for development work.

Custom Mandatory configuration

Whether roles are mandatory (or not) should also be customisable in Texture. For example, eLife specify that every peer-review contributor requires a role. However, Érudit may not require a role to be mandated for translators.

Taken from: https://github.com/elifesciences/TextureRequirements/issues/48

libero / editor