KMLM List

["Oliver Pesch" <OPesch@xxxxxxxxx>]

This is a timely discussion.  With release 4 of the COUNTER code of practice we 
are looking at ways to tighten up implementation of SUSHI through the creation 
of what could be considered a "Community Profile" for COUNTER and SUSHI that 
sets out expectations like this.  In addition, the thought is the COUNTER 
audit, would test the content provider's service against these expectations to 
make sure they are met before the audit is passed.

In the meantime, our expectation should be that the report name is as presented 
on the SUSHI site (http://www.niso.org/workrooms/sushi/reports/)  and that the 
content provider should correct the problem if they do not follow this.  

Thanks
Oliver

-----Original Message-----
From: sushidevelopers@xxxxxxxxxxxxx [mailto:sushidevelopers@xxxxxxxxxxxxx] On ;
Behalf Of Christian Jägle
Sent: Thursday, June 16, 2011 8:46 AM
To: sushidevelopers@xxxxxxxxxxxxx
Subject: [sushidevelopers] Reportname in SUSHI Request

Hi,

we met a problem with the spelling of the Reportname in the SUSHI XML 
Request.
Some Vendors allow upper- and lowercase (for example jr1A, JR1a...). 
Some expect a specific string. And here comes the problem. I would at 
least expect, that the spelling used in the SUSHI Reports Registry 
should work.
But we had a vendor, where we had to use "JR1A" for the request, "JR1a" 
did not work and I am quite shure that this will not be last Vendor with 
that or a similar problem (JR/BR/CR <-> Jr/Br/Cr would other good 
candidates)
We would have to store the exact spelling for every vendor to be sure of 
our SUSHI request.
I couldn't find a rule for that in the specification. but maybe I missed 
something. Is this a wrong implementation on vendor side?

Thanks
Christian Jägle


-- 
Christian Jägle

Albert-Ludwigs-Universität Freiburg
Universitätsbibliothek
Rempartstraße 10-16 | Postfach 1629
D-79098 Freiburg    | D-79016 Freiburg

Telefon:  +49 761 203-3886
E-Mail:   christian.jaegle@xxxxxxxxxxxxxxxxxx
Internet: www.ub.uni-freiburg.de

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.