RE: [jats-list] "Self citation" markup (NLM Archiving v3).

Subject: RE: [jats-list] "Self citation" markup (NLM Archiving v3).
From: "O'BEIRNE, Richard" <Richard.OBEIRNE@xxxxxxx>
Date: Fri, 13 Jul 2012 14:15:26 +0100
And different journals will have different citation styles (which I've always
found bizarre...), so displaying a hard-coded citation won't always solve the
problem. I would think the majority of authors will be using reference
management software to build their references.

Richard

-----Original Message-----
From: Evan Owens [mailto:eowens@xxxxxxx]
Sent: 13 July 2012 13:47
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: [jats-list] "Self citation" markup (NLM Archiving v3).

Hi Simon,

Interesting problem.   A few random observations:

There are attributes on given-names and surname  to capture initials.

We at AIP use <related-article related-article-type="translation source"> to
capture the information about where the original article appeared.   We
published some translation journals in the past where this was important
metadata.

Does this self-citation needed to be fielded (bibliographic elements marked
up) or could it just be a formatted string?   If the latter, then perhaps you
could put it as a block into a single <custom-meta> <meta-value>.  Or you
could use custom-meta for any single piece that there is no place for
elsewhere in article-meta.

Evan Owens
American Institute of Physics
eowens@xxxxxxx

-----Original Message-----
From: Newton, Simon - Edinburgh [mailto:snewton@xxxxxxxxx]
Sent: Friday, July 13, 2012 5:57 AM
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [jats-list] "Self citation" markup (NLM Archiving v3).

Hi Jeff,

Yes, reconstruction of a self-citation from metadata is acceptable in the
majority of journals, but some require a form that cannot be generated
reliably that way. For example we may be obliged to enter creators' full names
into the metadata, but also to publish a self-citation in which forenames are
reduced to initials (and it's quite hard automatically to do that reliably);
or the self-citation needs to contain an extra piece of text that details
where the original language version of the article was published, and this is
not elsewhere in the XML. There is also the issue where even if we produce a
selection of styles to build it automatically, some journals will always want
something different, and short of producing a rendering script tailored for
every one of our many journals this seemed to be the best way round that. The
trade-off is indeed a form of duplication.

Many thanks - Simon.

-----Original Message-----
Date: Thu, 12 Jul 2012 13:58:28 -0400
To: "jats-list@xxxxxxxxxxxxxxxxxxxxxx" <jats-list@xxxxxxxxxxxxxxxxxxxxxx>
From: "Beck, Jeff (NIH/NLM/NCBI) [E]" <beck@xxxxxxxxxxxxxxxx>
Subject: Re: [jats-list] "Self citation" markup (NLM Archiving v3).
Message-ID: <CC24880F.653BD%beck@xxxxxxxxxxxxxxxx>

Simon,

I would just consider this something to be handled by your rendering engine.
It should be able to build the citation directly from the <article-meta>, and
then you don't have to worry about duplicating that information in each
article.

Jeff

-----------------------------------------------------------------------------
-------------------------------
Blackwell Publishing Limited is a private limited company registered in
England with registered number 180277.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex,
United Kingdom. PO19 8SQ.
-----------------------------------------------------------------------------
-------------------------------

Oxford University Press (UK) Disclaimer

This message is confidential. You should not copy it or disclose its contents
to anyone. You may use and apply the information for the intended purpose
only. OUP does not accept legal responsibility for the contents of this
message. Any views or opinions presented are those of the author only and not
of OUP. If this email has come to you in error, please delete it, along with
any attachments. Please note that OUP may intercept incoming and outgoing
email communications.

Current Thread