KMLM List

[Nadia <nadia@xxxxxxxxxxx>]

Thanks Oliver.

Yes the 'requests' are already included in BR1 and BR2 reports.

So I am going to report the 'searches' only in BR5.

Thanks for your help.

On 02/10/2013 00:00, Oliver Pesch wrote:
> As I recall, the purpose of BR5 was to capture search activity where the system 
> allow searching on a selected book and thus hosts that don't have book-specific 
> searches would not offer BR5 since searches are captured at the database or 
> platform level.
>
> My recommendation would be the BR5 would focus on searches.  If you do have federated search 
> engines specifying searches for specific books, then you would want to report these separately from 
> the "regular" searches, but I would not include any of the "requests" since, as 
> you say, they are already covered in BR1 and BR2.
>
> Oliver
>
> -----Original Message-----
> From: sushidevelopers@xxxxxxxxxxxxx [mailto:sushidevelopers@xxxxxxxxxxxxx] On ;
> Behalf Of Nadia
> Sent: Tuesday, October 01, 2013 5:20 PM
> To: 'sushidevelopers@xxxxxxxxxxxxx'
> Subject: [sushidevelopers] BR5 report - Sushi question
>
> Hello,
>
> Another question on Appendix A in the Counter-Sushi implementation document for 
> Counter 4 please.
>
> Appendix A lists (ft_ps, ft_pdf, ft_html, ft_total) as valid metric types for 
> BR5 (Total Searches by Month and Title) report which has the 'Searches' 
> category and thus should rather have
>
> 'searches_fed and searched_reg) as valid metric types.
>
> OR does the 'Requests' category also apply to the BR5 report so (ft_ps, ft_pdf, 
> ft_html, ft_total) metric types are also valid for BR5.
> If it does, should the same be applied to BR3&  BR4 reports?
>
> Please advise.
>
> Many 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.
>
>