<$BlogRSDURL$>
Christina's LIS Rant
Sunday, March 11, 2007
  It's about trust, reliability, accuracy ...
Stacy on Web4Lib reported that a vendor provided obviously bad usage statistics (reporting usages of databases she doesn't have access to) and when questioned, they said simply that it was a "known issue" and that they would *hide* those stats from her. ARGH! So she apparently tried a few different ways to tell them that hiding-omitting-scrubbing bad stats isn't really the answer she needs. Then they said "trust me" about the rest of the statistics!!! Wha?

She also had this problem with another vendor:
This isn't the only vendor that provided inaccurate usage data this year.
Another vendor's statistics showed zero usage after our subscription
started. Since I had used it at the beginning of the subscription period,
it was clear something was wrong. When this anomaly was reported, the
vendor never explained what the problem was, but sent us some
completely different (and - surprise! - much higher) usage figures.

So, we're supposed to be using more scientific ways of evaluating our collection (usage factors, impact factors, weighting systems...) and being able to justify costs based on use and need. In fact, some would like to completely remove the professional judgment of the librarian and use only usage metrics (not MPOW, btw, we're sensible). If this is the crap we allow from our vendors, there's no way we can do these evaluations systematically and have them have any relationship to reality. (I'm not criticizing Stacy -- she's obviously not allowing this but fighting it!)

This vendor in question is specifically listed in the COUNTER documents so should have completed an audit by a CPA. These audits are supposed to help with credibility, reliability, and validity. Maybe the higher ups at the company don't know what their help desk people are telling librarians who call?

Update 3/26/2007: Since this post, I have been in contact with Michael Gorrell, Senior Vice President, Chief Information Officer and Kate Hanson of EBSCO. They have been doing some in-depth troubleshooting and have found a problem in an algorithm that led to the errant usage report. See their support site for more information: http://support.ebsco.com/support_news/detail.php?id=341&t=h. As I said in a private e-mail to Mr. Gorrell- my intent was not to criticize EBSCO directly as they do seem to be cognizant of the importance (generally) and are working to fix the problem (ever since it got escalated from the original help desk person). Once again, libraries are very heavily reliant on vendor-provided statistics for decision making which is a bit scary. Also Mr. Gorrell corrected an assumption I made -- COUNTER audits are for content and formatting, not for accuracy.... sigh.

Labels: , ,

 
Comments: Post a Comment


Powered by Blogger

This is my blog on library and information science. I'm into Sci/Tech libraries, special libraries, personal information management, sci/tech scholarly comms.... My name is Christina Pikas and I'm a librarian in a physics, astronomy, math, computer science, and engineering library. I'm also a doctoral student at Maryland. Any opinions expressed here are strictly my own and do not necessarily reflect those of my employer or CLIS. You may reach me via e-mail at cpikas {at} gmail {dot} com.

Site Feed (ATOM)

Add to My Yahoo!

Creative Commons License
Christina's LIS Rant by Christina K. Pikas is licensed under a Creative Commons Attribution 3.0 United States License.

Christina Kirk Pikas

Laurel , Maryland , 20707 USA
Most Recent Posts
-- Blogger meetup at ACRL?
-- Reading Star... I want to go classify something!
-- John Depuis interviews "See Jane Compute"
-- I'm under attack today
-- Who's Who? Me!
-- Lincoln on self-reliant library users
-- Good news from a society publisher: RSC launches ...
-- Flabbergasted: Springerlink has Google ads!
-- Memories of Lee S. Strickland
-- AAP hires a PR firm to fight back against open access
ARCHIVES
02/01/2004 - 03/01/2004 / 03/01/2004 - 04/01/2004 / 04/01/2004 - 05/01/2004 / 05/01/2004 - 06/01/2004 / 06/01/2004 - 07/01/2004 / 07/01/2004 - 08/01/2004 / 08/01/2004 - 09/01/2004 / 09/01/2004 - 10/01/2004 / 10/01/2004 - 11/01/2004 / 11/01/2004 - 12/01/2004 / 12/01/2004 - 01/01/2005 / 01/01/2005 - 02/01/2005 / 02/01/2005 - 03/01/2005 / 03/01/2005 - 04/01/2005 / 04/01/2005 - 05/01/2005 / 05/01/2005 - 06/01/2005 / 06/01/2005 - 07/01/2005 / 07/01/2005 - 08/01/2005 / 08/01/2005 - 09/01/2005 / 09/01/2005 - 10/01/2005 / 10/01/2005 - 11/01/2005 / 11/01/2005 - 12/01/2005 / 12/01/2005 - 01/01/2006 / 01/01/2006 - 02/01/2006 / 02/01/2006 - 03/01/2006 / 03/01/2006 - 04/01/2006 / 04/01/2006 - 05/01/2006 / 05/01/2006 - 06/01/2006 / 06/01/2006 - 07/01/2006 / 07/01/2006 - 08/01/2006 / 08/01/2006 - 09/01/2006 / 09/01/2006 - 10/01/2006 / 10/01/2006 - 11/01/2006 / 11/01/2006 - 12/01/2006 / 12/01/2006 - 01/01/2007 / 01/01/2007 - 02/01/2007 / 02/01/2007 - 03/01/2007 / 03/01/2007 - 04/01/2007 / 04/01/2007 - 05/01/2007 / 05/01/2007 - 06/01/2007 / 06/01/2007 - 07/01/2007 / 07/01/2007 - 08/01/2007 / 08/01/2007 - 09/01/2007 / 09/01/2007 - 10/01/2007 / 10/01/2007 - 11/01/2007 / 11/01/2007 - 12/01/2007 / 12/01/2007 - 01/01/2008 / 01/01/2008 - 02/01/2008 / 02/01/2008 - 03/01/2008 / 03/01/2008 - 04/01/2008 / 04/01/2008 - 05/01/2008 / 05/01/2008 - 06/01/2008 / 06/01/2008 - 07/01/2008 / 07/01/2008 - 08/01/2008 / 08/01/2008 - 09/01/2008 / 09/01/2008 - 10/01/2008 / 10/01/2008 - 11/01/2008 / 11/01/2008 - 12/01/2008 / 12/01/2008 - 01/01/2009 / 01/01/2009 - 02/01/2009 / 02/01/2009 - 03/01/2009 / 03/01/2009 - 04/01/2009 / 04/01/2009 - 05/01/2009 / 05/01/2009 - 06/01/2009 / 08/01/2010 - 09/01/2010 /

Some of what I'm scanning

Locations of visitors to this page

Search this site
(gigablast)

(google api)
How this works

Where am I?

N 39 W 76