KMLM List

[Nadia <nadia@xxxxxxxxxxx>]

Thanks Oliver.

Nadia Yassine nadia@xxxxxxxxxxx
ISSEL
Marketwave Web Analytics
http://www.issel.co.uk
Tel: +44 (0)870 166 2435

For support contact support@xxxxxxxxxxx

Registered in England and Wales No: 3218933
Registered Office: 1 Trinity Avenue, London N2 0LX


On 01/10/2013 18:13, Oliver Pesch wrote:
> It is best to think of CR2 as a consortium version of DB1 there a series of DB1 
> reports are returned (one per consortium member) in a single response; 
> therefore, the changes to DB1 also apply to CR2.  I will advise COUNTER about 
> the anomaly/oversight in the CR2 naming.
>
> Oliver
>
> -----Original Message-----
> From: sushidevelopers@xxxxxxxxxxxxx [mailto:sushidevelopers@xxxxxxxxxxxxx] On ;
> Behalf Of Nadia
> Sent: Tuesday, October 01, 2013 9:59 AM
> To: 'sushidevelopers@xxxxxxxxxxxxx'
> Subject: [sushidevelopers] Sushi - Counter 4 Question please
>
> Hello,
>
> I had a look this afternoon at the Appendix A of the Counter-Sushi 
> implementation document for Counter 4.
>
> It lists the metric types (result_clicks and record_views) as valid metric 
> types for the CR2 report.
>
> Is this a recent update to this implementation document or rather a mistake?
>
> The reason I am asking is because CR2 is titled (Total Searches by Month and 
> Database), thus have 'Searches' Category and should only have (searches_reg, 
> and searches_fed) as valid metric types.
>
> Why Appendix A lists the 'Requests' category alongside the 'Searches'
> category for the CR2 report?
>
> To my best knowledge only DB1 (Total Searches, Result Clicks and Record Views by 
> Month and Database) report should have both categories (Searches&   Requests).
>
> 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.
>
>