KMLM List

["Oliver Pesch" <OPesch@xxxxxxxxx>]

Yes, you are right... I missed the part of the CR1... And yes, the expectation 
is that the consortium report groups the data by customer not simple adds the 
customer element to each usage node.

 

Unfortunately I don't have any information about what HighWire is able to track 
for a consortium.

 

________________________________

From: Luiz Augusto Garcia da Silva [mailto:luizaugustogarcia@xxxxxxxxxxxx] ;
Sent: Saturday, July 17, 2010 9:02 AM
To: Oliver Pesch
Cc: luizaugustogarcia@xxxxxxxxxxxx; sushidevelopers@xxxxxxxxxxxxx
Subject: Re: [sushidevelopers] Someone got collect statistics from Highwire's 
SUSHI server?

 

Hello Oliver,

I undestood what you said about Highwire particularities.Nevertheless, I think 
that response sent by Highwire resulted from CR1 request is wrong. As we have a 
lot of members, report would be sent with data classified by each consortia 
member. This is the purpose of CR1. If Highwire doesn't have that information 
classified by member, I think that they would deny a request for a CR1.

I mentioned about requests to JR1 reports because as we are not getting collect 
data accordingly through CR1, the alternative would be collect data 
unclassified and put them in our database as an apart member.


Luiz.

On 16/07/2010 18:22, Oliver Pesch wrote: 

That is how they decided to implement because of the possibility of what I 
described.
--------------------------
Sent from my BlackBerry Wireless Handheld


----- Original Message -----
From: Luiz Augusto Garcia da Silva <luizaugustogarcia@xxxxxxxxxxxx> 
<mailto:luizaugustogarcia@xxxxxxxxxxxx> 
To: Oliver Pesch
Cc: sushidevelopers@xxxxxxxxxxxxx <sushidevelopers@xxxxxxxxxxxxx> 
<mailto:sushidevelopers@xxxxxxxxxxxxx> 
Sent: Fri Jul 16 15:42:33 2010
Subject: Re: [sushidevelopers] Someone got collect statistics from Highwire's 
SUSHI server?

The customer ID that I have used is related to the account of Sage
Journals. As I asked for a JR1 I expected only one entry for Customers,
and 393 entries for ReportItem, which is the amount of journals that we
subscribe at Sage.


On 16/07/2010 17:29, Oliver Pesch wrote:
> 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.
>
>
>
>   

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