KMLM List

[Marco van Schagen <marco@xxxxxxxxxxxxxxxxxx>]

Please share the location for the FAQ?Marco

On Mon, Apr 20, 2009 at 6:12 PM, Oliver Pesch <OPesch@xxxxxxxxxxxxx> wrote:

>  We are creating an FAQ to help guide implementors on issues like this and
> we will use this input to help get COUNTER to tighten up the code of
> practice.
>
> Thanks
> --------------------------
> Sent from my BlackBerry Wireless Handheld
>
> ------------------------------
>  *From*: Dennis Vaux
> *To*: sushidevelopers@xxxxxxxxxxxxx
> *Sent*: Mon Apr 20 11:09:07 2009
> *Subject*: RE: [sushidevelopers] Counter XML Question
>
> At Innovative, we have coded our SUSHI client to ignore any period counts
> for periods that span more than one month.   I agree that no one needs this
> "summary" data, but it isn't explicitly prohibited by the xsd, and we were
> unsuccessful when we tried to get Scholarly Stats to stop sending these
> summary counts in their SUSHI response when we first tested SUSHI 1.0 with
> them.
>
> -----Original Message-----
> *From:* Kim, Tae [mailto:Tae.Kim@xxxxxxxxxxxxxxxxxxxx]
> *Sent:* Friday, April 17, 2009 9:30 AM
> *To:* sushidevelopers@xxxxxxxxxxxxx
> *Subject:* [sushidevelopers] Counter XML Question
>
> I’m working with Proquest sushi service and they return the stats for every
> month and a total for all the months.
>
> For example if I ask for Jan-March, it returns something like:
> 2008-01-01 to 2008-01-31: 3 requests
> 2008-02-01 to 2008-02-28: 4 requests
> 2008-03-01 to 2008-03-31: 1 requests
> 2008-01-01 to 2008-03-31: 8 requests
>
> I’d LIKE to tell them that really, the last is redundant and spans multiple
> months so it shouldn’t be in the result.
> But really, I can’t find anything in the SUSHI or COUNTER standard that
> dictates that each data point should be exactly one month in duration.
>
> The xsd of course can’t really validate  anything like this.
>
> Can anybody point me to something in the standard? Usage stats spanning
> multiple months is kinda problematic for me and I imagine for other clients
> as well.
>
> Tae Kim
> Software Developer
> Serials Solutions
>
> 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.
>
>
>