KMLM List

["Oliver Pesch" <OPesch@xxxxxxxxx>]

A bit of background on that...

Because HighWire hosts content for several publishers, customers can have many 
identities.  From what I understand, the customer's HighWire account can be set 
up as an umbrella account for multiple publisher-specific accounts.  What I 
further understand is that if you request a JR1 specifying the Highwire 
Customer ID, they will return all journals; however, the publisher-specific 
customer ID is returned for each journal.  So it is different than CR1, but 
sort of feels the same.

Just something to look for when you are analyzing what they have sent.

Oliver

-----Original Message-----
From: sushidevelopers@xxxxxxxxxxxxx [mailto:sushidevelopers@xxxxxxxxxxxxx] On ;
Behalf Of Luiz Augusto Garcia da Silva
Sent: Friday, July 16, 2010 3:24 PM
To: sushidevelopers@xxxxxxxxxxxxx
Subject: [sushidevelopers] Someone got collect statistics from Highwire's SUSHI 
server?


     When we request for statistics from Highwire, the report cames in a 
wierd format. For example, if I request for a CR1 report, it cames with 
the same Customer repeating for each journal. When it would came with 
only one Customer and several entries for each Report Item enclosing 
performace information related to one journal. Indeed, is looks like a 
JR1 report disguised as a CR1.

The curious is that if I request a JR1 report the response is the same.

Did someone succeed in collecting statistics Highwire?

Thanks,
Luiz Augusto
__________________________________________________
Fale com seus amigos  de graça com o novo Yahoo! Messenger 
http://br.messenger.yahoo.com/ ;


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.