Article citation details

The volume, issue, issue title, season and page numbers OR elocation-ID under which the article will be published.

User Stories

Author

[x] As an author, I want to be able to see my article's pending citation details so that I can share them before publication.

Production staff

[x] As production staff, I want to be able to check the citation details for the article so that I can confirm they are correct before publication.
[x] As production staff, I want to be able to edit the citation details for the article so that I can change or correct citation details before publication.

Érudit

[ ] As production staff I want to be able to check the citation details to check that no errors were introduced during the digitization and electronic publication process.

But what if . . . ?

Different users of Texture have different requirements for this set of metadata, requiring some but not other fields and vice versa

Considerations

Because eLife ties volume to year, it is possible for these details to change between the author checking the proof and the final publication of the article (unless the article has already been published as an accepted manuscript). For example, an author can proof the article at the end of 2019 (vol 8) but it will not be published until the new year (2020, vol 9).
For eLife, pub-date year from collection should be derived from the main pub-date
Use of issue varies from publisher to publisher. eLife does not publish content into issues, only a single volume per year. Other journals publish many issues a year within a single yearly volume; still others have multi-volumes per year. Ultimately, the probably shouldn't any logic built in to Texture to relate issue, volume and year!
Print articles will require page-range information.
The JATS DTD does not allow a valid XML document to have elocation-id and page numbers - only one or the other.
@pub-type="collection" attribute on <pub-date> is a PMC requirement for eLife, but they are willing to change this requirement.
Some journals use the concept of a season and this must be explicit in the XML tagging
Some issues have titles and due to multi language input, a language attribute may be required on this field if it does not match the main language of the article.

XML requirements

Children of <article-meta>

<volume>8</volume>
<issue>2</issue>

For eLife, the elocation-id is always is same as publisher id prefixed with ‘e’, e.g. for an article with <article-id pub-id-type="publisher-id">46989</article-id>, the elocation-id is

<elocation-id>e46989</elocation-id>

For journals that publish page numbers instead of an elocation-id:

<fpage>67</fpage>
<lpage>101</lpage>

eLife example:

<pub-date pub-type="collection">
    <year>2016</year>
</pub-date>
<volume>5</volume>
<elocation-id>e00666</elocation-id>

Erudit example:

<pub-date date-type="collection">
   <season>printemps</season>
   <year>2012</year>
</pub-date>
<volume>44</volume>
<issue>2</issue>
<issue-title xml:lang="fr">Usages, discours et idéologies linguistiques dans la francophonie canadienne: perspectives sociolinguistiques</issue-title>
<fpage>67</fpage>
<lpage>101</lpage>

The seq attribute can be used to disambiguate documents that start at the same page:

...
<article-meta>
    ...
    <fpage seq="a">82</fpage>
    <lpage>82</lpage>
    ...
</article-meta>
...

libero / editor