Re: [jats-list] Versions of an article

Subject: Re: [jats-list] Versions of an article
From: Alf Eaton <eaton.alf@xxxxxxxxx>
Date: Thu, 9 May 2013 20:25:01 +0100
That's an interesting point to debate, and I think it mostly depends
on how much the content is likely to change between versions (in this
particular case it's article preprints, which could change
considerably between versions).

For example, F1000 Research mint DOIs only for each version of an article:
They still have a generic non-versioned URL for the article (as well
as the versioned URLs), but not an article-level DOI.

Dryad's guidelines <>, on the other
hand, recommend to have both a generic, over-arching DOI for all
versions of a dataset, as well as one DOI for each specific version of
the dataset. This seems like the most appropriate option, as it allows
someone to choose to cite either the whole "work" (possibly while
specifying a particular point in time) or a specific version, as they

There are also inevitably going to be different DOIs for the same
"work", if a preprint is published on one service (and assigned a
DOI), then published in its final form somewhere else and assigned a
new DOI by the different publisher. You could argue that preprints
shouldn't be assigned DOIs, but then you have to a) define when
something is a "preprint" and b) tell people that they're not allowed
to cite "unpublished" work using a DOI.


On 9 May 2013 18:11, Bruce Rosenblum <bruce@xxxxxxxxx> wrote:
> Alf,
> This isn't an answer to your question, but a comment about DOI. You should
> assign a DOI to a work, not a manifestation. If you assign a DOI to each
> version of an article, many applications will fail to link because you'll
> have multiple DOIs that have the same metadata. It's better to assign one
> DOI and then have the landing page show each version of the article.
> Bruce
> At 12:59 PM 5/9/2013, Alf Eaton wrote:
>> Does anyone have any experience with marking up links to previous
>> versions of an article in JATS, and also marking up the version number
>> of the current article?
>> The previous versions of the article will all have their own URLs and
>> DOIs, so I was thinking that the "related-article" element would make
>> sense. There doesn't seem to be an existing @related-article-type
>> attribute meaning "previous version", but HTTP link relations[1]
>> include "predecessor-version" and "successor-version", which could be
>> re-usable.
>> Thanks,
>> Alf
>> [1]
> -------------------------------------------------------------------
> This email message and any attachments are confidential. If you are not the
> intended recipient, please immediately reply to the sender or call
> 617-932-1932 and delete the message from your email system. Thank you.
> -------------------------------------------------------------------
> Bruce D. Rosenblum
> Inera Inc.
> 19 Flett Road
> Belmont, MA 02478
> 617-932-1932 (office)
> bruce@xxxxxxxxx

Current Thread