KMLM List

["Oliver Pesch" <OPesch@xxxxxxxxx>]

On the simplest level it would use something like the MISO client to make sure 
reports can be retrieved.  But, that still leaves some room for subjective 
interpretation of the standard.  The plan is to develop what would amount to a 
SUSHI/COUNTER Community Profile which would remove the subjectivity.  This may 
take the form of a detailed FAQ or some other form.

Some of the things that have some up on this list and would be included are:
- Report names in the request should be as specified in the "Report Registry" 
on the NISO SUSHI site.
- Date ranges for the usage dates must be included and follow the prescribed 
format.
- Do not include the "Totals" entries in the COUNTER XML
- The usage data returned should be for the dates requested (if that usage is 
available) -- and not for the entire year.
- The item Identifier ID tag must be included, BUT if there is not identifier 
the ID tag should be empty (e.g. <ID/> and not <ID>N/A</ID>)

Other things would be that the COUNTER report should validate against the 
COUNTER schemas on the NISO site (including the enumeration schema which will 
validate values for Metric Type, Categories, etc.)

This list is a good place to discuss concerns and confusions and suggestions.  
This is the group that has to make this all work!

Also, I wouldn't expect the audit of SUSHI to be enforced until COUNTER release 
4 -- which is in the works with a compliance target of end of 2013 (yes "13").

Thanks
Oliver

-----Original Message-----
From: james.wismer@xxxxxxxxxxxxxxxxxx [mailto:james.wismer@xxxxxxxxxxxxxxxxxx] ;
Sent: Thursday, June 23, 2011 7:25 AM
To: Oliver Pesch; sushidevelopers@xxxxxxxxxxxxx
Subject: RE: [sushidevelopers] What's A Standard For?

Oliver;

It would be helpful to know exactly what the SUSHI audit will entail so that 
service providers can do an internal audit of their service prior to a Counter 
audit.  This way we can look to address any issues ahead of the audit.

Can the specific test cases and methodology that will be employed for the SUSHI 
audit be posted to this list?

Thanks.
Jim Wismer

> -----Original Message-----
> From: sushidevelopers@xxxxxxxxxxxxx 
> [mailto:sushidevelopers@xxxxxxxxxxxxx] On Behalf Of Oliver Pesch
> Sent: Thursday, June 23, 2011 6:24 AM
> To: dehnhardt@xxxxxxxxxxx; sushidevelopers@xxxxxxxxxxxxx
> Subject: Re: [sushidevelopers] What's A Standard For?
> 
> 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.