RE: [jats-list] Metadata: version number of an article

["Lizzi, Vincent" <Vincent.Lizzi@xxxxxxxxxxxxxxxxxxxx>]

Hi Nikos,

I think it is also dependant on what information is useful to identify article
version in a particular environment. If you want to capture a version number
or a version date then <article-id> or <history><date> will work. If you want
to capture more information (perhaps a detailed change log), and have reason
to keep this information in the XML, then a customization may be your best
option. For the question Alf presented though, I would go with <article-id
pub-id-type="article-version"> as a readily available solution. :)

Best regards,
Vincent


-----Original Message-----
From: Nikos Markantonatos [mailto:nikos@xxxxxxxxxx]
Sent: Friday, April 11, 2014 11:42 AM
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [jats-list] Metadata: version number of an article

Hi Vincent.

In trying to answer Alf's question, I was more inclined to use the <history>
element, much like your suggested approach with the timestamp, or even a real
date. I was being held back by the lack of a version identifier in that
solution. But your alternative proposal using the <article-id> is excellent
and very much to the spirit of that tag. Of course, one can combine these
suggested solutions to maintain both the current version number as well as the
date history of previous versions.

I think these two solutions minimize the need for introducing a custom version
element to JATS.

Best regards,
Nikos Markantonatos
Atypon


On 04/11/2014 06:29 PM, Lizzi, Vincent wrote:
> Alf,
>
> This seems like a good use case for the <history> element. The next question
is how to tag version number using the elements allowed in <history>. If your
version numbering scheme happens to use timestamps this might work for you:
>
> <history><date date-type="article-version"
> iso-8601-date="2014-04-10T08:51:00Z"/></history>
>
> A different approach that would probably work better could be to use
<article-id>. Versioning is related to identifying a document so this seems
like a reasonable use of the article-id tag. In this usage the id is a
"Identifier assigned to a version of an article." instead of a "Unique
identifier assigned to an article." One might use the article-version
identifier in combination with an article identifier (such as DOI) to locate a
version of an article. For example:
>
> <article-id pub-id-type="article-version">1.0</article-id>
>
> An example with version numbers automatically assigned by subversion:
>
> <article-id pub-id-type="article-version">$Revision: 42 $</article-id>
>
> Another option that you could do is customize your local version of JATS to
add an element to hold article version. There is no tag in JATS currently to
capture the version of an article so this would be a reasonable extension.
>
> Vincent
>
>
> -----Original Message-----
> From: Alf Eaton [mailto:eaton.alf@xxxxxxxxx]
> Sent: Thursday, April 10, 2014 8:51 AM
> To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: [jats-list] Metadata: version number of an article
>
> I've been looking for a suitable tag for marking up the version number of an
article that can undergo multiple revisions. Is there anything more
appropriate than
"<custom-meta><meta-name>version</meta-name><meta-value>1.0</meta-value></cus
tom-meta>"?
>
> Thanks,
> Alf
>
>
> ----------------------------------------------------------------------
> ----------------------------------------------------------------------
>
>
>
> The information contained in this email message may be confidential. If you
are not the intended recipient, any use, interference with, disclosure or
copying of this material is unauthorised and prohibited. Although this message
and any attachments are believed to be free of viruses, no responsibility is
accepted by Informa for any loss or damage arising in any way from receipt or
use thereof. Messages to and from the company are monitored for operational
reasons and in accordance with lawful business practices.
> If you have received this message in error, please notify us by return
> and delete the message and any attachments. Further enquiries/returns
> can be sent to postmaster@xxxxxxxxxxx
>
>


--
Confidentiality Notice:  This email and any attachments are for the sole use
of the intended recipient(s) and contain information that may be confidential
and/or legally privileged.  If you have received this email in error, please
notify the sender by reply email and delete the message.  Any disclosure,
copying, distribution or use of this communication by someone other than the
intended recipient is prohibited.