KMLM List
View email archives for the history of this mailing list.
|
|
|
|
sushidevelopers - RE: [sushidevelopers] No report for searches grouped by journal?
|
Message Thread:
Previous |
Next
|
- To: Jordan Reiter <jordan@xxxxxxxx>, "sushidevelopers@xxxxxxxxxxxxx" <sushidevelopers@xxxxxxxxxxxxx>
- From: Oliver Pesch <OPesch@xxxxxxxxx>
- Date: Wed, 5 Jun 2013 00:50:31 +0000
- Send Email to sushidevelopers@list.niso.org:
- Send new message
- Reply to this message
|
There is no report for searches by Journal. Most content sites don’t perform searches on individual journals – most searches are on a set of content from many
journals. Note that very few platforms offer the book report for searches by title either for the same reason.
THanks
From: sushidevelopers@xxxxxxxxxxxxx [mailto:sushidevelopers@xxxxxxxxxxxxx]
On Behalf Of Jordan Reiter
Sent: Tuesday, June 04, 2013 5:50 PM
To: sushidevelopers@xxxxxxxxxxxxx
Subject: [sushidevelopers] No report for searches grouped by journal?
I've been looking over the Code of Practice document for COUNTER 4 and although there appears to be a searches by book report, there isn't a searches by journal report.
Is this correct -- there isn't a way to say "users performed x searches against Journal Foo and y searches against Journal Bar"?
--
Jordan Reiter
AACE - Association for the Advancement of Computing in Education
Email: jordan@xxxxxxxx | Website:
www.aace.org |
+1.267.438.2388
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.
|
|
|