Issue Identification

Every TF JATS article XML and issue XML is required to identify the journal issue that the file is a part of. For complete issues, and articles in build-issue-online/eFirst issues, this information should be repeated with consistency in all article XML files and in the issue XML file. For articles not yet assigned to an issue, "0" should be placed in the volume and issue elements and the article-status stage attribute should be set according to the article's stage.

In Article XML, the issue an article appears in should be identified in <article-meta>. In Issue XML, the issue identification should be tagged in <tf:issue-meta>.

Regular Issues

The volume should be tagged in the <volume> element and the issue should be tagged in the <issue> element. For example, for volume 40 issue 1:

<volume>40</volume>
<issue>1</issue>

For example, for volume 28 issue 3-4 (a combined-issue range):

<volume>28</volume>
<issue>3-4</issue>

Supplement Issues

Supplement issues should be tagged using the <supplement> element. The <issue> element must also be present and should contain a 0. The issue file name should have "S" followed by a number in the issue segment, and that number following "S" in the file name should match the number in the <supplement> element. For example, for volume 7 supplement 1:

<volume>7</volume>
<issue>0</issue>
<supplement>1</supplement>

For this example, assuming BHER as the journal acronym, the issue .zip file would be named: BHER_I_7_S1_J.zip

Articles not in an issue

For articles that will be publish outside of an issue, or that have not yet been assigned to an issue, the volume and issue elements should be set to 0. For example:

<volume>0</volume>
<issue>0</issue>

In Article XML, the stage attribute on tf:article-status should be set to "just-accepted" for at the tagging/AMO stage, or set to "ahead-of-issue" for a preview/final outside of issue version of the article.

Special Cases

Volume-Only Issues

A few journals use one incrementing number to identify each issue (instead of using separate volume and issue numbers). In these cases, the number should be tagged in <volume>, and <issue> should be set to 1 for all issues. An attribute content-type="volume-only" should be placed on the volume element. For example:

<volume content-type="volume-only">500</volume>
<issue>1</issue>

Occasionally there have been issues published as volume-only with a combined-issue range. When retrodigitizing issues that have this numbering, the range should be captured using the volume-only content-type. For example:

<volume content-type="volume-only">22-23</volume>
<issue>1</issue>

Multi-Part Issues

Occasionally there have been issues published as part A and part B with the same issue number. When retrodigitizing issues that have this numbering, the issue number should be placed in the <issue> element and the <issue-part> element should be used to capture the suffix of the issue number. For example:

<volume>5</volume>
<issue>3</issue>
<issue-part>A</issue-part>

For this example, assuming UJFM as the journal acronym, the issue .zip file would be named: UJFM_I_5_3A_J.zip