KMLM List

["Oliver Pesch" <OPesch@xxxxxxxxx>]

This is not as they should be.  SUSHI will be added to the formal Audit and 
these issues should be caught.

If you can send the publisher's name directly to me I will work with COUNTER to 
have them address the problem.

Thank you for reporting this.

Oliver
--------------------------
Sent from my BlackBerry Wireless Handheld


----- Original Message -----
From: Holger Dehnhardt [mailto:dehnhardt@xxxxxxxxxxx]
Sent: Thursday, June 23, 2011 04:44 AM
To: sushidevelopers@xxxxxxxxxxxxx <sushidevelopers@xxxxxxxxxxxxx>
Subject: [sushidevelopers] What's A Standard For?

Dear everybody,

recently I had to test the SUSHI service of a publisher, we had not integrated 
until now.
As always things did not went straight - in fact they were more tricky than 
usual.

We had to leave 
1.) both UsageDataRange fields blank to request the data for the current year
or 
2.) fill in 'YYYY-01-01' and 'YYYY-12-31' to request data for the last year.

The documentation declares the start and end fields as mandatory, so the 
request is not valid - but this publisher is listed as COUNTER 3 compliant.

Is this like things should be?

Holger

-- 
i.A. Holger Dehnhardt

Lehmanns Fachbuchhandlung GmbH 
siz | service internationale zeitschriften 
- international subscription agency -
Hardenbergstrasse 5 
10623 Berlin 
Deutschland / Germany

Tel.: +49 (0)30 617911 16
Fax.: +49 (0)30 617911 62
e-Mail: dehnhardt@xxxxxxxxxxx 
size.lehmanns.de
www.lehmanns.de 

Sitz der Gesellschaft: Köln, Amtsgericht Köln HRB 12268 
Geschäftsführer: Detlef Büttner
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.