KMLM List
View email archives for the history of this mailing list.
|
|
|
|
sushidevelopers - Re: [sushidevelopers] Problems when consolidating collected data
|
Message Thread:
Previous |
Next
|
- To: Oliver Pesch <OPesch@xxxxxxxxx>
- From: Luiz Augusto Garcia da Silva <luizaugustogarcia@xxxxxxxxxxxx>
- Date: Wed, 03 Nov 2010 16:13:40 -0200
- Cc: sushidevelopers@xxxxxxxxxxxxx
- Send Email to sushidevelopers@list.niso.org:
- Send new message
- Reply to this message
|
We are very frustrated with this. This task of classification in a
single library may be feasible, but in our consortium with dozens of
thousands e-resources, it is a painful task, if not impossible. Do
e-resources names and identifiers that come in COUNTER reports (often
identifiers missing or slightly differentnames) match with our KBs (SFX,
Verde) will be an Herculean task.
Luiz
On 10/27/2010 4:44 PM, Oliver Pesch wrote:
COUNTER does not require the content provider to limit statistics for
a consortium member to just those titles the subscribed to through the
consortium. Many (if not most) content providers would have no
ability to provide this level of filtering on their content host or
through the service that manages their usage -- basically the
consortium purchases are simply added to the content available to
consortium member on their account with the content provider.
The expectation is that the system you are using to manage your
statistics data would filter the results by the titles and databases
you subscribe to on behalf of your members. I know this is probably
not the answer you want to hear, but it is the reality of the situation.
Oliver
------------------------------------------------------------------------
*From:*sushidevelopers@xxxxxxxxxxxxx
[mailto:sushidevelopers@xxxxxxxxxxxxx] *On Behalf Of *Luiz Augusto
Garcia da Silva
*Sent:* Wednesday, October 27, 2010 1:18 PM
*To:* sushidevelopers@xxxxxxxxxxxxx
*Subject:* [sushidevelopers] Problems when consolidating collected data
Hello everyone,
We from CAPES Consortium are having many problems when consolidating
data collected from our publishers. The major cause of these problems
is that when we ask for a report from one publisher it sends us report
containing data from titles that we don't subscribe. An example occurs
when some of our members has contract with publisher out of consortium
scope. As an analogy, it's like if I request a bank statement and it
lists to me transactions of others who live in my house. Because of
that,we are having tremendous difficulty to calculate our usage
indicators.
Since numbers are distorted, we don't have an accurate usage measure,
even having a lot of statistics collected.
Shouldn't mechanisms for delivery of statisticsbe oriented just by the
contracts (either via web site or SUSHI),instead of be oriented by a
collection of IP addresses or a particular collection arrangement at
the publisher side?
Thanks,
Luiz Augusto
CONFIDENTIALITY NOTICE
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
|
- Re: [sushidevelopers] Problems when consolida, Luiz Augusto Garcia da Silva (you are here)
|
|