The unique identifiers for an article (internal publisher ID, DOIs etc)
User stories
As an author, I should be able to see the article ID so that I can use it for reference in conversation with production staff.
Production staff
As production staff, I should be able to see the DOI so that I know what it will be upon publication.
As production staff, I should be able to edit the DOI so that I can correct any errors.
But what if . . . ?
Consideration
The eLife article numbers are currently five digits long but this may need to increase in the future.
Érudit and SciELO and others will not have such a clear structure for their article numbers and will need letters, numbers and special characters allowed in this field, so it be not restricted.
The article number and DOI can be related or unrelated so no logic should be built on them being the same or similar values.
eLife predefines its DOIs and registers them with Crossref ahead of publication; SciELO and Érudit define their DOIs at the point of publication.
XML requirements
article-id elements with an appropriate @pub-id-type. Captured as a child of article-meta.
eLife has two:
Description
The unique identifiers for an article (internal publisher ID, DOIs etc)
User stories
Production staff
But what if . . . ?
Consideration
XML requirements
article-id
elements with an appropriate@pub-id-type
. Captured as a child ofarticle-meta
. eLife has two:SciELO uses one:
Érudit currently has none (added later on in the workflow using a different process)
Mock ups
Proposal