COUNTER and e-resource management tools Link Servers, Metasearch tools, ERM systems UKSG: December 2005 Jenny Walker VP Marketing Ex Libris Group
e-Resource Management Tools?
SIAM journal on applied mathematics
SUSHI
Standards Usage Statistics Harvesting Initiative Initial premise: too difficult/too expensive for libraries to get their statistics each month Goal: to retrieve and import COUNTER reports from compliant content providers into local systems automatically. Proof-of-concept uses Web (SOAP) services – COUNTER JR-1 report NISO workshop – early 2006
Tripped up by Terminology?
Platform/Service Publisher Journals
Interface Link Target e-journals
Search Target Collection?
e-Product (Interface) e-Product (Package) e-Product (e-journals)
Linking/Link Resolvers
COUNTER basics Q: Who gets to count full text requests? Publisher? Aggregator? E-Journal gateway? Link Resolver? A: The party that delivers the actual text to the user
Linking A&I Database Link Resolver Publisher site User finds citation of interest in an A&I database. An OpenURL link is provided Citation Link menu Full Text Link-Out Full text
JSTOR Annual Linking Totals * Total Accesses 50,279,12880,082,633131,510,667171,969,141226,509,990 Articles Viewed 7,928,40514,645,58925,934,99235,263,46360,795,293 Links to JSTOR 207,2781,453,7512,952,7604,728,9416,289,342 Links to Articles Viewed Ratio 2.61%9.93%11.39%13.41%11.74% * Year end projection By kind permission of JSTOR
Portals/Metasearch
Metasearch Also known as: Federated search Broadcast search User presented with a single search interface Searches multiple information sources at same time Eliminates (or assists with) resource selection Retrieve, consolidates and ranks results A new challenge for statistics
Metasearch: a new challenge What can be affected Session counts Search counts Why? “Search all” option or automatic selection/search of many resources Perform simultaneous activities Optimization techniques
Searching without Metasearch EBSCOOCLCProQuestOVID use r Resources -Product 1 -Product 2 -Product 3 … Visits = 1 Sessions = 2 Searches = 2
With Metasearch engine EBSCOOCLCProQuestOVID use r Metasearch -Search All -Business -Medicine … Visits = 1 Sessions = 20 Searches = 20
With Metasearch engine EBSCOOCLCProQuestOVID use r Metasearch -Search All -Business -Medicine … Visits = 1 Sessions = 28 Searches = 28
Metasearch lessons Libraries should want to isolate metasearch sessions and searches Capture source of activity Isolate metasearch IP address Have metasearch access through separate account Support metasearch standardization activities through NISO We need a standard way to recognize a metasearch session
e-Resource Reports and Stats Metasearch Tools Searches by Search Target Link Resolvers Clickthroughs per Journal Clickthroughs per Link Target ERM systems Cost-usage analysis Overlap analysis
Thank You Jenny Walker