<role>

Role or Function Title of Contributor

Title or role of a contributor to a work (for example, editor-in-chief, chief scientist, illustrator, research associate, conceptualization).

Remarks

What a Contributor Does:The role of a contributor may be relative to acquiring the data, performing the research, writing the paper, data visualization, or even an organizational or supervisional role. As an enabling standard, JATS is agnostic on this point, and a publisher, archive, aggregator, or other JATS user may identify <role> elements for contributors as they choose.
Who can Take a Role: In JATS, roles may be recorded for primary contributors (<contrib>, <contrib-group>, or <collab>), inside bibliographic citations for cited contributors (<element-citation>, <mixed-citation>, or <person-group>), inside a signature block (<sig-block>), or inside the descriptions of referenced materials (<product>, <related-article>, or <related-object>).
Content of Role: The content of a <role> element may be the name of a role, possibly recorded as a CRediT taxonomic term, the translation of such a term into another language, free text, a CRediT term with ‘free-text qualifiers’, or a term from a non-CRediT taxonomy.
CRediT Contributor Roles: The CRediT (Contributor Roles Taxonomy) Taxonomy (http://dictionary.casrai.org/Contributor_Roles) has been written to better define and communicate the different kinds of contributor roles in research outputs, and more and more publishers are defining the role of their contributors and collaborations. JATS therefore needs to be able to:
  • Attach role information to a contributor (<contrib>),
  • Support multiple roles for a single contributor,
  • Support CRediT terms to describe this role, but also non-CRediT terms as well as free-text qualifiers to terms, and
  • Be able to specify the term source (such as CRediT).
Role Attributes Record Taxonomy: If the content of the <role> element is a term from a taxonomy (ontology, thesaurus, term-list, vocabulary, industry glossary, or other known source), the vocabulary attributes should be used to record that source. This source is typically a formal ontology or taxonomy such as CRediT. Four attributes can be used in this Tag Set to identify a term from such a controlled vocabulary:
vocab
Name of the controlled or uncontrolled vocabulary, taxonomy, ontology, index, database, or similar that is the source of the term. For example, for a role, a value might be the CRediT taxonomy (“credit”) or MESH Headings (“mesh”). For an uncontrolled term, the value might be merely the word “uncontrolled”.
vocab-identifier
Unique identifier of the vocabulary, such as (but not limited to) a URI or DOI. For example, for Dublin Core (DCC), the identifier might be http://dublincore.org/documents/2012/06/14/dces/. For CRediT, the identifier might be http://dictionary.casrai.org/Contributor_Roles.
vocab-term
The content of the element is the free prose version of the vocabulary or taxonomic term. The @vocab-term attribute holds the canonical version of the same term, as it appears in the vocabulary. For example, if the attribute value was “Writer - original draft”, the element might contain the display text “Author”.
vocab-term-identifier
Unique identifier of the term within a specific vocabulary, such as (but not limited to) an item number, an accession number, a URI, a DOI, etc.
CRediT Best Practice: Although the @content-type attribute on the element <role> is designed to accept any text as its value, Best Practice is to tag the CRediT taxonomy of contributor roles when such use is possible. CRediT roles, might include, for example, “Conceptualization” (Ideas; formulation or evolution of overarching research goals and aims.), “Data curation” (Management activities to annotate [produce metadata], scrub data and maintain research data [including software code, where it is necessary for interpreting the data itself] for initial use and later reuse.), or “Writing – original draft” (Creation and/or presentation of the published work, specifically writing the initial draft.) Additional non-CRediT values such as “deep sea diver” may also be used. If a single contributor played more than one role in the creation of an article, the <role> element may be repeated, with a different @content-type attribute for each.

Related Elements

Contributor Roles: Information on the role or type of contribution made by a contributor, group of contgributors, or collaboration is collected in two places: For example, the <contrib> element’s @contrib-type attribute might have a value of “editor”, whereas the content of the <role> element could be “Associate Editor”. As another example, the <contrib> element’s @contrib-type attribute might be “author”, whereas the content of the <role> element is a CRediT taonomy term for the type of author contribution.
When the content of role is taken from a controlled vocabulary, teaxomony, thesaurus, index, database, or similar, the <role> element is preferred over a type attribute, because a <role> can be explicitly tied to its taxonomy using the JATS vocabulary attribute, and because the element <role> can repeat, making it possible to record a person or group in more than one role in the creation of an article.
On Behalf Of: This element joins the related element <on-behalf-of> in describing the contribution of a contributor. The <role> element will say that a person is an “Editor” or “Associate Editor”, and the <on-behalf-of> element will state that this editing was undertaken as a representative of a group or organization
See discussion about <on-behalf-of> in Remarks.

Attributes

Content Model

<!ELEMENT  role         (#PCDATA %role-elements;)*                   >

Expanded Content Model

(#PCDATA | bold | fixed-case | italic | monospace | overline | roman | sans-serif | sc | strike | underline | ruby | sub | sup | named-content | styled-content)*

Description

This element may be contained in:

Example 1

As part of contributor information:
...  
<contrib-group content-type="conference-editors">
<contrib contrib-type="editor">
<name name-style="western">
<surname>Herrera</surname>
<given-names>Gerardo</given-names>
</name>
<role>Conference Editor</role>
</contrib>
</contrib-group>
...
...
<contrib-group>
<contrib contrib-type="author">
<name name-style="western">
<surname>Foster</surname>
<given-names>Bill</given-names>
<prefix>Rep.</prefix>
</name>
<role>(IL-14)</role>
</contrib>
</contrib-group>
...

Example 2

As part of contributor information, with CRediT taxonomy shown:
...
<contrib-group>
<contrib>
<string-name><given-names>Barbara</given-names> <surname>Johnston</surname></string-name>
<role vocab="CRediT" 
vocab-identifier="http://dictionary.casrai.org/Contributor_Roles"
vocab-term="Conceptualization" vocab-term-identifier="http://dictionary.casrai.org/Contributor_Roles/Conceptualization">
study designer</role>
</contrib>
<contrib>
<string-name><given-names>Brooke</given-names> <surname>Jackson</surname></string-name>
<role vocab="CRediT" 
vocab-identifier="http://dictionary.casrai.org/Contributor_Roles"
vocab-term="Writing - Original Draft"
vocab-term-identifier="http://dictionary.casrai.org/Contributor_Roles/Writing_%E2%80%93_original_draft">
writer</role>
</contrib>
</contrib-group>
...

Example 3

Shown in a contributor group in context:
...
<article-meta>
<article-id pub-id-type="pmid">...</article-id>
<title-group>...</title-group>
<contrib-group>
<contrib contrib-type="author">
<name><surname>Forster</surname>
<given-names>Anne Williams</given-names>
</name>
<role>research physiotherapist</role>
<xref ref-type="aff" rid="StLukes"/>
<xref ref-type="aff" rid="RoyalInf"/>
</contrib>
<contrib contrib-type="author">
<name><surname>Young</surname>
<given-names>John G.</given-names></name>
<role>consultant physician</role>
<xref ref-type="aff" rid="RoyalInf"/>
<author-comment><p>on behalf of the Day Hospital
Group</p></author-comment>
</contrib>
</contrib-group>
<aff id="StLukes">Department of Health Care
for the Elderly, St Luke&#x2019;s Hospital, Bradford BD5
0NA</aff>
<aff id="RoyalInf">Academic Section
of Geriatric Medicine, Royal Infirmary, Glasgow
G4 0SF</aff>
<pub-date publication-format="print" date-type="pub" iso-8601-date="1999-03-27">
...</pub-date>
...
</article-meta>
...

Example 4

In a mixed-style bibliographic reference (punctuation and spacing preserved):
...
<ref>
<mixed-citation>
<string-name><surname>Johnson</surname>,
<given-names>D. H.</given-names></string-name>,
<string-name><surname>O&rsquo;Neil</surname>,
<given-names>T. A.</given-names></string-name>,
<role>managing directors</role>.
<source>Wildlife habitat relationships in Oregon
and Washington</source>.
<publisher-loc>Corvallis, Oregon, USA</publisher-loc>:
<publisher-name>Oregon State University Press</publisher-name>;
<year iso-8601-date="2001">2001</year>.
</mixed-citation>
</ref>
...

Example 5

In an element-style bibliographic reference (punctuation and spacing removed):
...
<ref>
<element-citation>
<person-group person-group-type="director">
<name><surname>Johnson</surname>
<given-names>D. H.</given-names></name>
<name><surname>O&rsquo;Neil</surname>
<given-names>T. A.</given-names></name>
</person-group>
<role>managing directors</role>
<source>Wildlife habitat relationships in Oregon
and Washington</source>
<publisher-loc>Corvallis, Oregon, USA</publisher-loc>
<publisher-name>Oregon State University Press</publisher-name>
<year iso-8601-date="2001">2001</year>
</element-citation>
</ref>
...