◇◆

<volume-id> Volume Identifier

Name or identifier (for example, DOI) that describes an entire volume.

Usage/Remarks

The <volume-id> element holds an external identifier, typically assigned to a volume of a publication by a publisher. The contents of this element should not be confused with the @id attribute, which holds an internal document identifier that can be used by software to perform a simple link inside the document.

Attribute Best Practice

Type of Identifier Best Practice

Best Practice is to use the @pub-id-type attribute to indicate the type of the external identifier, such as a publisher’s identifier, a DOI, a PMID, an aggregator’s or archive’s identifier, the identifier assigned by an indexing or hosting service, or similar. (See @pub-id-type for values.)

Authority for Identifier Best Practice

The attribute @assigning-authority should name the organization or system that assigned the identifier or administers the identifier (such as Crossref, OCLC, GenBank, Figshare).
Historical Note
Until JATS version 1.2d2 (2018), the @pub-id-type’s value conflated two meanings: the attribute could hold the type of identifier (such as a DOI or ISBN), or it could hold the name of the organization or system that defined or registered the identifier (such as Crossref). There was no way to state both that the identifier content of the element was a DOI and that the server was Figshare or Crossref. Although all the previous @pub-id-type values will continue to be accepted, for Best Practice, the @assigning-authority should name an organization, and the @pub-id-type attribute should describe the identifier type.
Related Elements
The related element <volume> holds the volume number as published with the journal.
Attributes
assigning-authority
content-type
hreflang
pub-id-type
specific-use

Base Attributes

id
xml:base
xml:lang

Linking Attributes

xlink:actuate
xlink:href
xlink:role
xlink:show
xlink:title
xlink:type

Namespaces

xmlns:xlink
Models and Context
May be contained in
<article-meta>, <element-citation>, <front-stub>, <mixed-citation>, <product>, <related-article>, <related-object>, <volume-issue-group>
Description
Any combination of:
Content Model
<!ELEMENT  volume-id    (#PCDATA %volume-id-elements;)*              >
Expanded Content Model

(#PCDATA | email | ext-link | uri | inline-supplementary-material | related-article | related-object | hr | bold | fixed-case | italic | monospace | overline | overline-start | overline-end | roman | sans-serif | sc | strike | underline | underline-start | underline-end | ruby | alternatives | inline-graphic | inline-media | private-char | chem-struct | inline-formula | tex-math | mml:math | abbrev | index-term | index-term-range-end | milestone-end | milestone-start | named-content | styled-content | fn | target | xref | sub | sup | x)*

Tagged Samples
<article-meta> 
...
<front>
 <journal-meta>
  <journal-title-group>
   <journal-title>The Indian Medical Gazette</journal-title>
  </journal-title-group>
  ...
 </journal-meta>
 <article-meta>
  ...
  <title-group>
   <article-title>The Indian Medical Gazette</article-title>
  </title-group>
  <pub-date pub-type="ppub" iso-8601-date="1866-01-01">
   <day>01</day>
   <month>1</month>
   <year>1866</year>
  </pub-date>
  <volume>1</volume>
  <volume-id pub-id-type="barcode" 
    assigning-authority="nlm">NLM015999052</volume-id>
  <issue>1</issue>
  <issue-id pub-id-type="archive" content-type="scantrac-id" 
    assigning-authority="nlm">70184</issue-id>
  <fpage>1</fpage>
  <lpage>1</lpage>
  ...
 </article-meta>
</front>
...
In citations 
...
<ref>
 <mixed-citation publication-type="journal" publication-format="print">
  <article-title>Edith Cavell: At Erpingham Gate, Norwich Cathedral</article-title>. 
  <source>Hospital</source>, <year iso-8601-date="1919">1919</year>; 
  <volume>66</volume>(<issue>1720</issue>): <fpage>177</fpage>-<lpage>187</lpage>. 
  <volume-id pub-id-type="barcode" assigning-authority="nlm">NLM037496842</volume-id>.
 </mixed-citation>
</ref>
...