An article may be assigned to one or more categories for indexing purposes. These can include subject areas, human-readable article types, collection names and so on.
User Stories
Author
As an author, I want to see the categories applied to my article so that I can confirm this is correct.
Production staff
As production staff, I want to be able to change the article categories so that I can correct any errors.
As production staff, I want to be able to add custom categories to an article so that I can compile ad-hoc collections or search terms.
As production staff, I want to be able to add categories in multiple languages so that I can include translated subject areas, article types etc.
But what if . . . ?
a publisher has specific display requirements for a category? Should this be reflected in the proof?
Considerations
This is covering terms applied at the article heading level. Keywords, which can be applied at the article level or on a more granular level throughout the article are covered in #23. These are distinct in JATS and tend to get referred to as separate entities.
Categories can include preset lists of terms (e.g. the major subject areas a journal is organised into, the list of article types it publishes etc).
At eLife, one or two major subject areas are allowed per research-type article. Non-research content does not need to have an MSA, but can have one.
Éruidt needs support for multiple levels of categories, up to a maximum of 3 levels.
Beyond subject areas, eLife sorts articles into types. E.g. Research article, Tools and resources, Short report, Editorial, Insight etc. These are human-readable types and do not always reflect the NLM article-type value included in article. For example, Research article, Tools and resources, Short report, Registered report, Replication study and Research communication all share the 'research-article' value for @article-type.
eLife also supports an additional 'subsection' category that is used to prefix the title in non-research content. This is currently captured in <subj-group subj-group-type="sub-display-channel"> within the <article-categories> group; however this is a legacy of our previous hosting platform. Allowing this is a requirement, but we are open to changing how it is captured. The published display of this 'subsection' label looks like:
Érudit and other publishers need to support categories in multiple languages.
XML requirements
Major subject areas at eLife are captured as <subject> elements in a <subj-group subj-group-type="heading"> element. They are captured as children of article-categories. 0-2 subjects allowed in eLife articles
<article-categories>
<subj-group subj-group-type="heading">
<subject>Epidemiology and Global Health</subject>
<subject>Human Biology and Medicine</subject>
</subj-group>
</article-categories>
Description
An article may be assigned to one or more categories for indexing purposes. These can include subject areas, human-readable article types, collection names and so on.
User Stories
Author
Production staff
But what if . . . ?
Considerations
article
. For example, Research article, Tools and resources, Short report, Registered report, Replication study and Research communication all share the 'research-article' value for@article-type
.<subj-group subj-group-type="sub-display-channel">
within the<article-categories>
group; however this is a legacy of our previous hosting platform. Allowing this is a requirement, but we are open to changing how it is captured. The published display of this 'subsection' label looks like:XML requirements
Major subject areas at eLife are captured as
<subject>
elements in a<subj-group subj-group-type="heading">
element. They are captured as children ofarticle-categories
. 0-2 subjects allowed in eLife articleseLife are not wedded to the
@subj-group-type
value given.@xml:lang
can be used on thesubj-group
element if needed.Subjects and keywords are currently under JATS4R public review
eLife defines article type as a
subject
infront/article-meta/article-categories
Example of
article-categories
for an article withsub-display-channel
(as mentioned in the considerations):Érudit need the ability to allow multi-language
subj-group
s:Mock ups
Proposal