KMLM List

["Oliver Pesch" <OPesch@xxxxxxxxx>]

One consideration with a COUNTER report is the systems that will consume
the reports.  When the usage is being loaded into a system like a usage
consolidation module, the identifier serves as a match point so you can
ensure the usage is being attributed to the correct title in the
library's collection.  The DOI has the advantage of being unambiguous;
however, the downside is that for the DOI to be useful, the knowledge
would have to have been pre-populated with the DOI for the journals,
books, etc. in question.  I would guess that most library catalogs do
not include the DOI as I don't know it is a standard identifier included
in MARC records.  There is also some question about which identifier is
most appropriate for identifying the "work" - I know the ISTC is being
considered.  For serial publications the ISSN-L is being viewed as a
solution to identify the "work" for the purpose of linking (I am not
aware of any such option of ISBNs thought.)  All this to say that moving
away from the well-known ISSN and ISBN will cause problems for those
that would consume the reports you create.

 

Having said that, the XML version of the COUNTER report does allow for
multiple identifiers to be included and the DOI is one of the valid
identifiers.  This means that for the XML version of your reports you
can include the ISBN and the DOI and even a proprietary identifier.
Below is the list of allowed identifier types.

Type

For use with

Description

Online_ISSN

ItemIdentifier

ISSN of the online version

Print_ISSN

ItemIdentifier

ISSN of the print edition

Online_ISBN

ItemIdentifier

ISBN of the online version

Print_ISBN

ItemIdentifier

ISBN of the print version

DOI

ItemIdentifier

Digital Object Identifier

Proprietary

ItemIdentifier

For publisher or vendor specific identifiers

 

 

________________________________

From: sushidevelopers@xxxxxxxxxxxxx
[mailto:sushidevelopers@xxxxxxxxxxxxx] On Behalf Of BAKER, Chris
Sent: Friday, July 09, 2010 5:00 AM
To: sushidevelopers@xxxxxxxxxxxxx
Subject: [sushidevelopers] ISBN field in COUNTER reports

 

This is not, exclusivelya SUSHI question  but I feel certain that people
on this list are among the right ones to discuss it, so I hope you don't
mind me raising it.

 

Many COUNTER reports require an ISBN and ISSN field.

Publishers often have many ISBNs -including ones that do not affect the
content that the customer sees  e.g. paperback and hardback ISBNs or
ISBNs for various sales offerings (such as bundles of titles).#

 

Which ISBNs do you use?

 

Some of us at OUP have been musing about suggesting to COUNTER that the
ISSN or ISBN fields ought to be replaced by a DOI (Digital Object
Identifier) field. Our thinking is this -  the idea of quoting an ISSN
or ISBN is to give the librarian a reference with which she can compare
usage of the same content from two suppliers (we think). If that is so,
then the modern way of unambiguously identifying a piece of content is
the DOI.

 

Your thoughts please!

 

We have thought of one caveat abotu thsi idea (maybe you can think of
more)-

Do many people make format assumptions abotu the ISBN and ISSN fields
when they process SUSHI or manually downloaded COUNTER reports? (E.g.
you might assume that the ISBN field will always be a 13-digit numeral -
This assumption would become wrong if DOIs were used instead)? 

 

 

 

 

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.



CONFIDENTIALITY NOTICE

This email and any files transmitted with it are confidential
and solely for the use of the intended recipient. It may contain
information which is covered by professional or other privilege.
If you are neither the intended recipient of this email nor the 
person responsible for delivering it to the intended recipient, 
be advised that you have received this email in error and that 
any use of it is strictly prohibited. Please notify the sender 
immediately by reply email and then delete it from your system. 
EBSCO accepts no liability for any loss or damage suffered by 
any person arising from the use of this email.

Please consider the environment before printing this email.