Re: [jats-list] about elocation-id and fpage

[久保田壮一 <kubota@xxxxxxxxx>]

Dear Bruce,

Thank you for you message.
I understand what you wrote.
I remember the discussion in CrossRef TWG.

> 1. Use only a DOI for the AOP version, and then traditional pagination for
> the print version.

We build DOI-name with the value in elocation-id field so we can
correlate AOP version with print version with DOI. I will consider it.

> 2. Use an elocation-id for the AOP version, and continue to use only the
> elocation-id in the print version. This strategy is used by many publishers
> including the American Physical Society. Of course the elocation-id should
> be supplemented with a DOI.

This is not hard to accept because for journals where they regard
print version as the authenticated version, the key bibliographic
element is page number, not article id. But some journals (e.g.
journals in physics) adopt this method.

Also I would like to consider using other fields like <article-id>.

>
> Note that when using elocation-ids (or article IDs, as they are more
> commonly called), there are best-practices promoted by NFAIS. Please see
> section 7 of the document
> http://www.nfais.org/files/file/Best_Practices_Final_Public.pdf.

Thank you for the information.

I would like to hear the practices of journal publishers.

Best wishes,
Soichi Kubota

2012/6/27 Bruce Rosenblum <bruce@xxxxxxxxx>:
> Dear Soichi,
>
> It is not a best-practice to have both an article ID and also page numbers.
> That's in part because secondary publishers will only index the article
> using one or the other, but if researchers cite the article sometimes with
> the article ID and other times by page number then it will cause great
> difficulty in creating a link to the item. There was also a somewhat heated
> discussion about publishers trying to use both elocation-ids and page
> numbers on the CrossRef TWG list several years back and the general
> consensus was that using both was not a good idea.
>
> There are several alternate solutions to this problem:
>
> 1. Use only a DOI for the AOP version, and then traditional pagination for
> the print version.
>
> 2. Use an elocation-id for the AOP version, and continue to use only the
> elocation-id in the print version. This strategy is used by many publishers
> including the American Physical Society. Of course the elocation-id should
> be supplemented with a DOI.
>
> Note that when using elocation-ids (or article IDs, as they are more
> commonly called), there are best-practices promoted by NFAIS. Please see
> section 7 of the document
> http://www.nfais.org/files/file/Best_Practices_Final_Public.pdf.
>
> Best regards,
>
> Bruce
>
> At 07:11 PM 6/26/2012, =?ISO-2022-JP?B?GyRCNVdKXUVEQVQwbBsoQg==?= wrote:
>>
>> Dear all,
>>
>> My name is Soichi Kubota from Japan Science and Technology Agency.
>> We operate an electronic journal platform, on which a number of
>> Japanese societies publish their journals.
>>
>> I would like to discuss about "ahead of print" article XML.
>>
>> First, an "ahead of print" version article is published online with
>> only an article id.
>> And then the final version (with full bibliographic information, such
>> as volume number, issue number, pages) is also published online
>> afterward.
>>
>> We use "elocation-id".element to identify article with no pages of
>> "ahead of print" version article.
>> Then it will have page numbers when it become final version which
>> corresponds to print version.
>> So the XML file of the final version should have both elocation-id and
>> fpage/lpage.
>> It is similar to the situation one journal may have both print ISSN/online
>> ISSN.
>>
>> But JATS dtd prohibits coexistence of elocation-id and
>> fpage/lpage/page-range.
>> I think they need not to be prohibited.
>>
>> I would like JATS dtd to permit the coexistence of elocation-id and
>> fpage/lpage/page_range.
>>
>> I would also be grateful if you give us how you correlate AOP version
>> with print version in one XML.
>> Thank you.
>>
>> Best wishes,
>> Soichi Kubota
>> ---
>> Japan Science and Technology Agency
>> Group of Electronic Journals
>> Soichi Kubota
>> email: kubota@xxxxxxxxx
>
>
> -------------------------------------------------------------------
> 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