RUP wiki - New Article Types Procedure

New Article Types Procedure

New Article Type Procedures and Notes

When a new article type is requested by editorial, it takes a few weeks to get going. Internally, first get basic information from managing or executive editor. You can send them this handy form:

https://goo.gl/forms/yfoEUdihG6C0i7W63

Then, the following info needs to be provided to HighWire, Sherdian, and EJP/JPS.

HighWire – Open a Salesforce case

Highwire requires us to use the following checklist (also available as a Google doc that can be downloaded, edited, and attached to a Salesforce case)

1) What is the singular display of the new section?

2) What is the plural display of the new section?

3) Should the entire section be free from access control by section rule?

4) Should the new section be included in the "Newest Articles" area of the homepage?

5) Should the new section be included in the "Reviews & Opinions" area of the homepage?

6) Is the displayed toc section specified in the 2nd hierarchical level?

7) Does the toc section, or any articles in it, need any special UI treatment?

8) What journals should have this new section enabled?

9) Will this section appear in ahead-of-print alerts? If yes, where in the ordered list of sections should it appear?

In addition, please provide the following:

Provide HW with earliest possible publication date (batch 1 for targeted issue) and delivery date for that batch
Provide <article-type> and <subject> (nested) and request a configuration update to display only the 2nd level subject on article
Provide sample files ASAP (XML, PDF, etc). [we have skipped this for article types that are exactly the same as existing ones]

And these should be done internally:

Add to navigation menu if necessary (RUP internal task)
Should article type appear in "Most read" widget? If not, it needs to be turned off here (this is an RUP internal task):
- http://hwmaint.jcb.rupress.org/stats/cgi-bin/rc_section_mgr.pl
- http://hwmaint.jem.rupress.org/stats/cgi-bin/rc_section_mgr.pl
- http://hwmaint.jgp.rupress.org/stats/cgi-bin/rc_section_mgr.pl

--------------------------------------------------------------------------------------------------------

Sheridan

New PFX template?
Harvard vs. numbered references - if numbered, specify that PFX should not alphabetize the reference list
eXtyles updates
Any need for eXtyles export update?
Crossmark?
TOC order
Workflow type: Major = AEX; Minor = Traditional Comp

Note: Erinn needs to create TypeFi template

Sample email request:

We’d like to add a new JGP article type, ‘Research News’, to be published in February.

This will fall into a ‘major’ workflow category, requiring AEX composition.

Erinn is working on the TypeFi template.

Details:

Will look exactly like JCB In Focus, except for the article type head..

Should not include Crossmark

eXtyles TOC head = News

JATS @article-type = news

JATS <subj-group subj-group-type="heading"> = News/Research News

Will appear as follows on the TOC:

Editorial

In Memoriam

Research News

Meeting Summary

Generally Physiological

Milestone in Physiology

Review

Viewpoint

Perspective

Commentary

Research Article

Hypothesis

Methods and Approaches

Tutorial

Addendum

Correction

Retraction

Meeting Abstracts

Please take care of any necessary updates to Artemis, PFX, eXtyles, and JATS export

----------------------------------------------------------------------------------------------------

eJP

Invited or open submission?
Bypass copyright splash screen (for free article types), defaulting to Green form?
Sent to SJS for screening? (Default is to NOT SEND for screening)

JPS

eXtyles TOC head = JATS @article-type =J
JATS <subj-group subj-group-type="heading"> =
Author, production, or invited
Content #: [EJP or specify convention if generated in JPS]
Free License type?
Ready for online release rules
TOC order

EJP/JSP support email sample:

We’d like to add a new JGP article type, ‘Research News’, to be published in early January.