Article type/category and subject area display and editing

[JGilbert-eLife]

(This is the first issue to be opened as part of the 'elife-next' category which details our requirements for Texture as a production tool)

In order to use Texture as a production/proofing tool at eLife, we would need to be able to view and edit the article-categories -

                <subj-group subj-group-type="display-channel">
                    <subject>Research Article</subject>
                </subj-group>
                <subj-group subj-group-type="heading">
                    <subject>Computational and Systems Biology</subject>
                </subj-group>
                <subj-group subj-group-type="heading">
                    <subject>Epidemiology and Global Health</subject>
                </subj-group>
            </article-categories>```

'display-channel' = article type (preset list)
'heading' = major subject area, 1 or 2 required

[michael]

Could we make it more explicit and use unique group names. E.g. "heading-1" and "heading-2" ? Or are these headings on the same level.

[JGilbert-eLife]

They're different kinds of categories, so I'm not quite sure how to classify their relationship in that fashion. While they're not quite the same level, neither are they in the hierarchical relationship heading-1 and heading-2 would imply.

What do you think @Melissa37? I know we used "display-channel" and "heading" because those are JATS recommended values, but is there scope to use something more explicit like "article-type" and "subject-area"?

[Melissa37]

Hi there

https://jats.nlm.nih.gov/archiving/tag-library/1.2d1/element/subj-group.html

I think "display-channel" and "heading" and are a thrownback from our time with another hosting vendor and I'd be happy to revisit these terms, but would like to do it in conjunction with a group like JATS4R. There is a keywords group currently in session - I'll take this to them.

Cheers M

[klawsonvt]

Hello Melissa et. al.,

The Subjects and Keywords sub-group met today and we discussed this. We reviewed the tagging snippet posted first in the thread, too.

It seems like the main question is about use of the @subject-group-type value itself. If so, the sub-group, at least at this point, is not planning to recommend a specific list of values to use (e.g., display-channel, heading), like how footnote types suggestions were handled in the JATS online documentation, for instance (https://jats.nlm.nih.gov/archiving/tag-library/1.2d1/attribute/fn-type.html). We would recommend leaving the values up to the user.

We noticed that the three subject groups in the example are on the same level. The two heading-related subject groups could be nested in the display-channel group if that is the intended relationship. This would be similar to what some of us do for deliveries to online hosts - where there might be a scientific category at the top level and then a multiple sub-categories nested [e.g., Social Sciences might be at the top level, and Environmental Sciences and Cognitive Sciences might be (nested) at a lower level in order to organize the articles better on the TOC].

Would you please let me know if there are any questions or if we have misunderstood? We are still working on the 1st draft for the JATS4R Steering Committee, so it is not too late to make suggestions to review! Seeing real world examples like this is helpful.

Kevin

[Melissa37]

HI @klawsonvt

Thanks for looking at this with your group! It's good to have the JATS4R feedback :-)

I am with @JGilbert-eLife on this as I don't think we consider them as hierarchical. I am thinking about how we'd arrange them in an issue TOC the 'display-channel' could trump the 'heading' simply because it would be unusual for a journal to mix editorial content such as editorials and commissioned commentaries in with the research content but then again the 'heading' could trump the 'display-channel' if we mixed the types of content according to the subject area. I am kinda thinking out loud here!! On balance, I think by not having a TOC and issues has freed us from that dilemma. Our home page, which could be seen as a TOC, publishes our editorial (magazine) content in a different thread to the research and the research is listed on date only. Content can be filtered by 'display-channel' or 'heading'.

[fabiobatalha]

Hello @Melissa37 @JGilbert-eLife

This is also one feature expected by Érudit in the next round of developments.

We are using this data structure to organize the issue toc, the following topics describes our use case.

• At this moment we are not concerned to classify the subject content with the attribute subj-group-type.
• The subject can be organized hierarchically
• We have a maximum of 3 subject levels (for hierarchical organization)
• Article can not be placed (classified) in more then one subject-group in the issue toc
• More then one subject-group is accepted only for translations.

Issue TOC in Érudit: https://www.erudit.org/fr/revues/rabaska/2016-v14-rabaska02663/

XML Sample:

      <article-categories>
        <subj-group>
          <subject>Place Publique</subject>
          <subj-group>
            <subject>Points de vue</subject>
            <subj-group>
              <subject>Livres</subject>
            </subj-group>
          </subj-group>
        </subj-group>
        <subj-group xml:lang="en">
        ...
        </subj-group>
      </article-categories>

[michael]

See keywords feature in requirements document.