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] JR5 - Sushi Question Message Thread: Previous | Next
  • To: "'sushidevelopers@xxxxxxxxxxxxx'" <sushidevelopers@xxxxxxxxxxxxx>
  • From: Nadia <nadia@xxxxxxxxxxx>
  • Date: Wed, 02 Oct 2013 15:28:11 +0100
Send Email to sushidevelopers@list.niso.org:
Send new message
Reply to this message
Thanks for the clarification.

On 02/10/2013 15:22, Oliver Pesch wrote:
The JR5 report only has room for one metric type -- total full text downloads 
-- so ft-total is the one.
--------------------------
Sent from my BlackBerry Wireless Handheld


----- Original Message -----
From: Nadia [mailto:nadia@xxxxxxxxxxx]
Sent: Wednesday, October 02, 2013 09:16 AM Central Standard Time
To: 'sushidevelopers@xxxxxxxxxxxxx'<sushidevelopers@xxxxxxxxxxxxx>
Subject: [sushidevelopers] JR5 - Sushi Question

Hello,

Another question on Appendix A in the Counter-Sushi implementation
document for Counter 4 please.

I can only see (ft_total) listed as valid metric type for the JR5
(Number of successful Full-Text Article Requests) by Year-of-Publication
(YOP) and Journal) Report.

Should not we also have (ft_html, ft_pdf or ft_ps) metric types here as
well?

Please advise.

Thanks

Nadia

EBSCO Industries<http://www.ebscoind.com/>


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.


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