Help

Icon - KMLM List KMLM List

View email archives for the history of this mailing list.

List Home All Archives Dates Threads Authors Subjects
sushidevelopers - RE: [sushidevelopers] Counter XML Question Message Thread: Previous | Next
  • To: <sushidevelopers@xxxxxxxxxxxxx>
  • From: "Dennis Vaux" <dvaux@xxxxxxx>
  • Date: Mon, 20 Apr 2009 09:09:07 -0700
Send Email to sushidevelopers@list.niso.org:
Send new message
Reply to this message
Counter XML QuestionAt 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

By Date: Previous | Next Current Thread By Thread: Previous | Next

  Mail converted by the most-excellent MHonArc 2.6.16