<front-stub>

Stub Front Metadata

Reduced set of metadata for use in <sub-article> and <response>, both of which are contained within an article. Any metadata not explicitly tagged in the front-stub is inherited from <article-meta> in the enclosing article.

Remarks

Usage: A front stub is used when a publisher or archive chooses not to repeat all the article metadata (such as the article publishing information, the journal metadata, and the issue metadata) for an embedded component such as a sub-article, but assigns that sub-article only the metadata (such as title, first page, and possibly contributor) that is particular to it, which it does not share with the main article. The assumption is that the sub-article will inherit any metadata elements from <article-meta> and <journal-meta> in the enclosing article that are not defined explicitly in the <front-stub>.
In this Tag Set, the set of possible metadata elements for the <front-stub> is exactly the same as the possible metadata elements for the entire article (<article-meta> inside <article>). The two are the same because, while the metadata for the stub will almost always contain many fewer elements, this Tag Set does not wish to predict which elements a given publisher or archive will leave out. It is a business decision how much metadata to place inside a sub-article.

Attributes

id Document Internal Identifier
xml:base Base

Content Model

<!ELEMENT  front-stub   %front-stub-model;                           >

Expanded Content Model

(article-id*, article-categories?, title-group?, (contrib-group | aff | aff-alternatives | x)*, author-notes?, pub-date*, volume*, volume-id*, volume-series?, issue*, issue-id*, issue-title*, issue-sponsor*, issue-part?, volume-issue-group*, isbn*, supplement?, (((fpage, lpage?)?, page-range?) | elocation-id)?, (email | ext-link | uri | product | supplementary-material)*, history?, permissions?, self-uri*, (related-article | related-object)*, (abstract)*, trans-abstract*, (kwd-group)*, funding-group*, conference*, counts?, custom-meta-group?)

Description

The following, in order:

This element may be contained in:

<response>, <sub-article>

Example 1

As part of a sub-article: 
    
<article dtd-version="1.1"  xmlns:xlink="http://www.w3.org/1999/xlink"
article-type="research-article">
<front>
<journal-meta>
<journal-id journal-id-type="nlm-ta">J Athl Train</journal-id>
<journal-title-group>
<journal-title>Journal of Athletic Training</journal-title>
</journal-title-group>
<issn publication-format="print">1062-6050</issn>
<publisher>...</publisher>
</journal-meta>
<article-meta>...</article-meta>
</front>
<body>...</body>...
<sub-article article-type="article-commentary">
<front-stub>
<title-group>
<article-title>COMMENTARY</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<string-name>
<surname>Kirk</surname>,
<given-names>Susan E.</given-names>
</string-name>
<aff>Susan E. Kirk, MD, is Assistant Professor in Internal
Medicine and Obstetrics and Gynecology, Division of Endocrinology
and Metabolism, University of Virginia Health System,
Charlottesville, VA.</aff>
</contrib>
</contrib-group>
</front-stub>
<body>...</body>
...</sub-article>
</article>

Example 2

As part of a response: 
    
<article dtd-version="1.1"  article-type="discussion" 
xmlns:xlink="http://www.w3.org/1999/xlink">
<front>
<journal-meta>
<journal-id journal-id-type="nlm-ta">BMJ</journal-id>
<journal-id journal-id-type="publisher-id">BR MED J</journal-id>
<journal-title-group>
<journal-title>BMJ : British Medical Journal</journal-title>
</journal-title-group>
<issn publication-format="print">0959-8138</issn>
<issn publication-format="electronic">1468-5833</issn>
<publisher>
<publisher-name>British Medical Journal</publisher-name>
</publisher>
</journal-meta>
<article-meta>...</article-meta>
</front>
<body>...</body>
<response response-type="discussion">
<front-stub>
<title-group>
<article-title>For</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<string-name>
<surname>Strube</surname>,
<given-names>George</given-names>
</string-name>
<role>general practitioner</role>
<aff>33 Goffs Park Road, Crawley, West Sussex RH11 8AX</aff>
<email>GStrube@aol.com</email>
</contrib>
</contrib-group>
</front-stub>
<body>...</body>
<back>...</back>
</response>
...</article>

Journal Archiving and Interchange Tag Library NISO JATS Version 1.1 (ANSI/NISO Z39.96-2015)

Version of December 2015

Back to Top