KMLM List

["Oliver Pesch" <OPesch@xxxxxxxxxxxxx>]

This definitely was something that was discussed in meetings and the
conclusion was the same as yours, there is no need to include the
summary nodes in the file as it just adds bulk and provides no
meaningful additional data.  XML is being loaded into a database systems
and adding things up is something these systems are good at.

 

It might be helpful if we are to add a COUNTER FAQ to the SUSHI site.
We can also enhance the in-schema documentation for COUNTER to clarify
that only the monthly numbers are needed. 


This is something we can take up with the Maintenance Committee.

 

Thanks

Oliver

 

________________________________

From: Kim, Tae [mailto:Tae.Kim@xxxxxxxxxxxxxxxxxxxx] ;
Sent: Friday, April 17, 2009 11: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.