KMLM List

[Oliver Pesch <OPesch@xxxxxxxxx>]

We discussed this at today's SUSHI Standing Committee Meeting and hope to have 
the updated reports and metric type "registries" available within a week. 

To answer your question -- DB3 is not PR1.

Also, you will see changes in Metric Types...

We have added...  ft_ps_mobile, ft_pdf_mobile, ft_html_mobile
We have removed... ft_mobile, ft_openaccess

These changes reflect the fact that there are now separate reports for showing 
Open Access and use of Mobile devices.

The R4 schemas (with the exception of the metric type changes in the 
COUNTERElements schema) remain unchanged.

Thanks
Oliver

-----Original Message-----
From: sushidevelopers@xxxxxxxxxxxxx [mailto:sushidevelopers@xxxxxxxxxxxxx] On ;
Behalf Of Luke Holt
Sent: Thursday, April 12, 2012 11:51 AM
To: SUSHIdevelopers@xxxxxxxxxxxxx
Subject: [sushidevelopers] COUNTER-SUSHI 4

I'm currently working on a COUNTER SUSHI 4 web service and noticed that the 
documentation is still based on the COUNTER 4 draft proposal.  Now that COUNTER 
4 has been published, I wondered when the new COUNTER SUSHI content would be 
finalized.

Specifically I'm interested in how to deal with the renaming of Database Report 
3 to Platform Report 1.  Would the web service need to accept a type of DB3 or 
PR1 for that?

Lucas Holt
</PRE>

<BR><BR>

<B><A 

href="http://www.ebscoind.com";> EBSCO Industries </B> 

</A> <BR><BR><PRE>
<font size ="1">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.</font>