[Web4lib] Cost per search

[K.G. Schneider]

> As budgets get tighter, we need to look critically at the cost of our
> databases compared to their usage. I'm interested in knowing what kind of
> cost per search other libraries - mainly public, as databases hold a
> different place in the mission of academic libraries -expect to see.
> 
> When we divide the number of searches by the cost of the database, we get
> costs ranging from under $1.00 per search to almost $30 per search.  I
> don't know if these are good numbers or bad. We also have databases on
> consumer topics, financial topics, etc. Should we have different criteria
> for different kinds of databases?

Well, if you restrict yourself to the cost-per search, you're comparing
database-to-database, not database-to-outcome. If it's a $30 search that
would in the past absorb $200 of serials or reference materials acquired on
a just-in-case scenario (accompanied by costs related to cataloging, shelf
space, etc.), then its value changes in relationship to what you're getting.


Also, in terms of the total cost of search, don't forget any ancillary tools
you may be using (federated search products, proxy servers, etc.) that pad
the cost. 

Plus another question I have is WHY a search costs that much. Obviously
there is a price/usage equation. But you may have some great stuff that's
hidden under a bushel, and the most popular resources may point to
satisficing behavior based on what's most visible or what resources they are
routinely guided towards. 

I'm not quibbling with the overall concept of assessing databases and making
sure you have the right mix and the right bang for your buck. I just think
it's more complex than an absolute cost-per-search (although that's a
logical place to begin). 

Karen G. Schneider