KMLM List

["Oliver Pesch" <OPesch@xxxxxxxxx>]

The intent of that error is a mechanism by which the content provider
and "report" that they have not yet processed or have available any
usage.  For example, if you ask for usage for August 2010 now, you would
expect that error.  Likewise, if you asked for usage for, let say, 2005
and the content provider only retains current year, plus 2 years of
usage data.

 

So this is not an error to be used to report zero usage for a particular
title, but rather, an error to report when the request is out of scope
related to overall usage available on the content provider's site.

 

Note that one client behavior when getting a 3030 error, is to wait a
day or two and try the request again.

________________________________

From: sushidevelopers@xxxxxxxxxxxxx
[mailto:sushidevelopers@xxxxxxxxxxxxx] On Behalf Of Boerema, Cate
Sent: Friday, July 23, 2010 12:48 PM
To: sushidevelopers@xxxxxxxxxxxxx
Subject: [sushidevelopers] "No Usage Available for Requested Dates"
Error

 

I need a little clarification on an error in the SUSHI Protocol document
(http://www.niso.org/kst/reports/standards/kfile_download?id%3Austring%3
Aiso-8859-1=Z39-93-2007.pdf&pt=RkGKiXzW643YeUaYUqZ1BFwDhIG4-24RJbcZBWg8u
E4vWdpZsJDs4RjLz0t90_d5_ymGsj_IKVa86hjP37r_hKQ00ioOP35WMjpxEaIkC50lEAytQ
p1kLJGhhtjwcI3V).  Page 13 states that error 3030 (No Usage Available
for Requested Dates) should be thrown when "Service did not find any
data for the date range specified."


But, according to the Counter CoP page 10
(http://www.projectcounter.org/r3/Release3D9.pdf):
 
Journals for which the number of full-text article requests is zero in
every month
should be included in Journal Report 1, except where an aggregator or
gateway is
responsible for recording and reporting the usage (see Section 7 below).

 

So, is error 3030 meant for cases where usage is null as opposed to
zero?  Is it correct to assume that nulls will be thrown when the
library doesn't subscribe to the journal(s) in question during the
specified date range?

 

Thanks,

 

Cate Boerema

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.