KMLM List

[Oliver Pesch <OPesch@xxxxxxxxx>]

Just to wrap this up.  I received the following response from Peter Shepherd at COUNTER.

 

“As you point out JR3 does not cover Accesses Denied and this should not be referred to in the text. I shall correct this text in the Appendix.”

 

Thanks

 

From: sushidevelopers@xxxxxxxxxxxxx [mailto:sushidevelopers@xxxxxxxxxxxxx] On Behalf Of Oliver Pesch
Sent: Wednesday, June 19, 2013 8:20 AM
To: tkampouris@xxxxxxxxxx; sushidevelopers@xxxxxxxxxxxxx
Subject: RE: [sushidevelopers] Tracking Turnaways on JR3 and TR3

 

Judging by the nature of this report and the change in name, it appears that the focus is on successful Full Text Requests by page type.  However, I do see one contradiction in Appendix H so I will send a note to Peter Shepherd to confirm.

 

Thanks

 

From: sushidevelopers@xxxxxxxxxxxxx [mailto:sushidevelopers@xxxxxxxxxxxxx] On Behalf Of Haris Kampouris
Sent: Wednesday, June 19, 2013 8:08 AM
To: sushidevelopers@xxxxxxxxxxxxx
Subject: [sushidevelopers] Tracking Turnaways on JR3 and TR3

 

Hello,

 

I am trying to figure out if we still need to keep track of turnaways on Journal Report 3.

from

NISO SUSHI Protocol:COUNTER-SUSHI Implementation Profile (Approved:August 10, 2012)

JR3: Number of Successful Item Requests and Turnaways by Month, Journal,and Page-Type Journal

JR3 mobile: Number of Successful Item Requests by Month, Journaland Page-Type for usage on a mobile device.

TR3: Number of Successful Item Requests by Month, Title, and Page Type

 

However, from the COUNTER Code of Practice for e-Resources Release 4 Appendix H

the Full-Text PDF Turnaways and Full-Text HTML turnaways page types have been removed from the example provided (comparing with the Counter 3 document).

thanks,
Haris

EBSCO Industries

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.