Presentation
advertisement
Connecting E-Resource Management Systems and Usage Statistics IFLA ERMS Satellite Meeting Cape Town, South Africa August 16, 2007 Oliver Pesch EBSCO Information Services opesch@ebsco.com Overview • Brief history of usage statistics for e-resources • ERM systems are well suited for usage statistics • Reporting potential of the ERM • Challenges faced for successful reporting • COUNTER • SUSHI (Standardized Usage Statistics Harvesting Initiative) • Looking ahead Overview • Brief history of usage statistics for e-resources • ERM systems are well suited for usage statistics • Reporting potential of the ERM • Challenges faced for successful reporting • COUNTER • SUSHI • Looking ahead 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 Timeline … Online collections use grows… ICOLC Guidelines release 1 ICOLC Guidelines rel 2 COUNTER formed COUNTER COP release 1 ERMI committee formed First commercial ERM released SUSHI committee formed COUNTER COP rel. 2 SUSHI as draft standard ICOLC endorses SUSHI COUNTER audit SUSHI released COUNTER COP rel 3 Timeline 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 …. 1997 1996 …. … Online collections use grows… ICOLC Guidelines release 1 ICOLC Guidelines rel 2 COUNTER formed online resources become significant COUNTER COP release 1 formed ERMI committee • libraries need to measure use First commercial ERM released SUSHI committee formed • not all vendors provide usage reports COUNTER COP rel. 2 • reporting inconsistent SUSHI as draft standard ICOLC endorses SUSHI COUNTER audit SUSHI released COUNTER E-resource usage grows • COP rel 3 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 Timeline … Online collections use grows… ICOLC Guidelines release 1 ICOLC Guidelines rel 2 COUNTER formed • consortia buying more e-resources COUNTER COP release 1 ERMI committee formed • troubled by lack ofconsistent reporting First commercial ERM released SUSHI committee formed • developed guidelines for usagereporting COUNTER COP rel. 2 • normalized terminology SUSHI as draft standard • set expectations for vendor reporting ICOLC endorses SUSHI COUNTER audit SUSHI released COUNTER ICOLC Guidelines for usage released COP rel 3 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 Timeline … Online collections use grows… ICOLC Guidelines release 1 ICOLC Guidelines rel 2 COUNTER formed • Refined guidelines COUNTER COP release 1 ERMI committee formed First commercial ERM released SUSHI committee formed COUNTER COP rel. 2 SUSHI as draft standard ICOLC endorses SUSHI COUNTER audit SUSHI released COUNTER ICOLC Guidelines release 2 COP rel 3 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 Timeline … Online collections use grows… ICOLC Guidelines release 1 ICOLC Guidelines rel 2 COUNTER formed • ICOLC guidelineshelped, but… COUNTER COP release 1 ERMI committee formed • Inconsistencies in counting and formatting First commercial ERM released formed SUSHI committee • Libraries, publishers and aggregators formed COUNTER COP rel. 2 COUNTER SUSHI as draft standard ICOLC endorses SUSHI • Developed code of practice for… COUNTER audit • Consistent, comparable and credible usage SUSHI released COUNTER Project COUNTER formed COP rel 3 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 Timeline … Online collections use grows… ICOLC Guidelines release 1 ICOLC Guidelines rel 2 COUNTER formed • Clarified terminology (consistent COP release 1 with other COUNTER standards) ERMI committee formed First commercial ERM released formed • Addressed web log and double-click issues SUSHI committee COUNTER COP rel. 2 • Identified specific reports (journals and SUSHI as draft standard databases) ICOLC endorses SUSHI COUNTER audit • Specified formatting and delivery SUSHI released COUNTER COUNTER code of practice – release 1 COP rel 3 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 Timeline … Online collections use grows… ICOLC Guidelines release 1 ICOLC Guidelines rel 2 COUNTER formed • Managing e-resources problematic COP release 1 COUNTER formed ERMI committee • Many libraries developing their own solution First commercial ERM released committee formed SUSHI • Committee formed to collaborate onCOUNTER the COP rel. 2 on the problem SUSHI as draft standard ICOLC endorses SUSHI • Work sponsored by DLF COUNTER audit • Final report published in 2004 SUSHI released COUNTER ERMI Committee formed COP rel 3 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 Timeline … Online collections use grows… ICOLC Guidelines release 1 ICOLC Guidelines rel 2 COUNTER formed • Innovative Interfaces, Inc.COP release 1 COUNTER formed ERMI committee • Based on ERMI functional specifications First commercial ERM released SUSHI committee formed • Served as a pilot to the ERMI work COUNTER COP rel. 2 SUSHI as draft standard ICOLC endorses SUSHI COUNTER audit SUSHI released COUNTER First commercial ERM released COP rel 3 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 Timeline … Online collections use grows… ICOLC Guidelines release 1 ICOLC Guidelines rel 2 COUNTER formed • Consolidated usage reporting being added COP release 1 COUNTER to ERM systems. ERMI committee formed First commercial ERM released • Based on COUNTER Journal Report 1 formed SUSHI committee COUNTER COP rel. 2 • Effort to retrieve reports was great SUSHI as draft standard ICOLC endorses SUSHI • Consistency issues continued COUNTER audit • Standardized Usage Statistics Harvesting SUSHI released Initiative formed to automate and simplify COUNTER SUSHI Committee formed COP rel 3 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 Timeline … Online collections use grows… ICOLC Guidelines release 1 ICOLC Guidelines rel 2 COUNTER formed • Clarified formatting expectations COP release 1 COUNTER formed ERMI committee • Added key data elements to reports First commercial ERM released SUSHI committee formed • Introduced the need for an audit COUNTER COP rel. 2 SUSHI as draft standard ICOLC endorses SUSHI COUNTER audit SUSHI released COUNTER COUNTER code of practice release 2 COP rel 3 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 Timeline … Online collections use grows… ICOLC Guidelines release 1 ICOLC Guidelines rel 2 COUNTER formed • Efforts sponsoredby NISO COUNTER COP release 1 ERMI committee formed • Successful pilots completed late 2005 First commercial ERM released SUSHI committee formed 2006 • Standard finalized in September COUNTER COP rel. 2 • Introduced as draft standard for trial use SUSHI as draft standard ICOLC endorses SUSHI COUNTER audit SUSHI released COUNTER SUSHI released as draft standard COP rel 3 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 Timeline … Online collections use grows… ICOLC Guidelines release 1 ICOLC Guidelines rel 2 COUNTER formed • Trial of standard was a success COP release 1 COUNTER ERMI committee formed • Minor adjustmentsmade to clarify and First commercial ERM released address concerns SUSHI committee formed COUNTER COP rel. 2 • Presented to ballot as Z39.93 in July SUSHI as draft standard ICOLC endorses SUSHI COUNTER audit SUSHI released COUNTER SUSHI standard under ballot COP rel 3 Overview • Brief history of usage statistics for e-resources • ERM systems are well suited for usage statistics • Reporting potential of the ERM • Challenges faced for successful reporting • COUNTER • SUSHI • Looking ahead ERMs are suited for usage consolidation • Intended to manage all e-resources • Intended as a single place to record all information about those resources • Tie-in to global knowledge bases • Data relationships Data relationships Products Platform E-journals Packages/ Databases E-books Data relationships Publisher E-journal Hosted on Package Platform Data relationships Blackwell Abacus Synergy Blackwell Synergy Collection EBSCOhost Academic Search Premier Data elements (partial list) • Descriptive information - Package names, resource names, etc. • Identifiers - ISSNs, ISBNs, package identifiers, etc. • Subject headings • URLs (link to resource) • Rights and restrictions for content use • Coverage information • Cost information • Usage information • And much more... (ERMI identified more than 300 data elements) Questions an ERM can answer • Which packages and databases are available from a given vendor? • Which resources are included with a database or package? • In which databases and packages will a given resource be found? • On what platforms (interfaces) can a database or package be accessed? • What databases or packages can be accessed on a given platform? • What resources can be accessed on a given platform? • What resources were included in a given deal? - From what vendor(s)? - On what platform? Overview • Brief history of usage statistics for e-resources • ERM systems are well suited for usage statistics • Reporting potential of the ERM • Challenges faced for successful reporting • COUNTER • SUSHI • Looking ahead ERM systems and usage E-journal Hosted on Platform Data relationships Packages/ Platform E-journals Databases Academic Search Premier Blackwell Synergy Collection Synergy EBSCOhost Abacus Usage Statistics Resource Platform Usage Abacus EBSCOhost 5,400 Abacus Synergy 3,600 Full text usage reports • Which journals are most/least used in the collection • Report by platform, or • Aggregate usage across all platforms • Summarize by platform to determine the platforms generating the most full text views Data relationships Packages/ Platform E-journals Databases Academic Search Premier Blackwell Synergy Collection Synergy EBSCOhost Abacus Usage Statistics Resource Platform Usage Abacus Synergy 5,400 Abacus EBSCOhost 3,600 Cost analysis • Combine usage with cost data • Cost per use is an indicator of value - The higher the use, the lower the cost per use • Assist with collection management Cost analysis Combining Sorting and Cumulative Totals Link out reports • • • • • Uses link resolver and A-to-Z activity A quick view of how the collection is being used Identify most productive sources of links Identify most used targets Does not require loading vendor usage (but neither is it comprehensive) Database reports • Track searches and sessions • Discover which databases are being used • Use for marketing (perhaps patrons are not finding the databases) • Budget management Overlap analysis • Determine overlap between packages and databases • Includes coverage overlap as well as title overlap • Identify redundant packages or databases • Combined with usage data to determine which overlapping databases are most used Benchmark reports • • • • Possible with hosted services Compare a library with peer libraries Collection analysis Usage analysis Overview • Brief history of usage statistics for e-resources • ERM systems are well suited for usage statistics • Reporting potential of the ERM • Challenges faced for successful reporting • COUNTER • SUSHI • Looking ahead Challenges • COUNTER reports are key - Inconsistencies in formatting remain - Excel not the best format for loading into automated systems • Gathering and processing the reports is time-consuming - Many vendors - Many sites log in to - Many reports to pull - Many different procedures The Usage Statistics Gathering Enterprise for Libraries Challenges • COUNTER reports are key - Inconsistencies in formatting remain - Excel not the best format for loading into automated systems • Gathering and processing the reports is time-consuming - Many vendors - Many sites log in to - Many reports to pull - Many different procedures • Identifiers Overview • Brief history of usage statistics for e-resources • ERM systems are well suited for usage statistics • Reporting potential of the ERM • Challenges faced for successful reporting • COUNTER • SUSHI • Looking ahead • Non-profit organization includes librarians, publishers and aggregators • Lead in the standardization of usage - How use is counted - How use is reported • “Consistent, credible, comparable” http://www.projectcounter.org/ COUNTER Code of Practice • Code of Practice first released Jan 2003 • Release 2 released Jan 2006 • Code of Practice Addresses: - Terminology - Layout and format of reports - Processing of usage data - Delivery of reports http://www.projectcounter.org/code_practice.html COUNTER Usage Reports Journal Reports: • JR1: Full Text Article Requests by Month and Journal • JR2: Turnaways by Month and Journal Database Reports: • DB1: Total Searches and Sessions by Month and Database • DB2: Turnaways by Month and Database • DB3: Searches and Sessions by Month and Service Books and Reference Works: • Title Requests, Section Requests, Searches and Turnaways Journal Report 1: Number of Successful Full-Text Article Requests by Month and Journal Explicit report layout – “consistent” “Credible” – COUNTER Audit • Effective now, an audit must be passed for a vendor’s service to be compliant • Conducted by auditor certified accountant or by organization accredited by COUNTER (ABCE) • At vendor expense Overview • Brief history of usage statistics for e-resources • ERM systems are well suited for usage statistics • Reporting potential of the ERM • Challenges faced for successful reporting • COUNTER • SUSHI • Looking ahead SUSHI: Objectives • Solve the problem of harvesting and managing usage data from a growing number of providers. • Promote consistency in usage formatting (XML) • Automate the process SUSHI: What is it? • An XML Message • Methods to transfer the message between two systems • Implemented as a Web service • Using SOAP (Simple Object Access Protocol) SUSHI : The Exchange Report Request <Requester> <Customer Reference> <Report Definition> Report Response <Requester> <Customer Reference> <Report Definition> <Report as payload> SUSHI Architecture • The next series of slides graphically show a SUSHI transaction - Library system requests a usage report - SUSHI client makes the request - SUSHI server processes request - SUSHI server prepares COUNTER report - SUSHI server “packages” and returns response - SUSHI client processes COUNTER report The Library and Content Provider’s systems are both connected to the internet. Library Content Provider Internet The SUSHI client is software that runs on the library’s server, usually associated with an ERM system. Library Content Provider ERM SUSHI Client Internet The SUSHI server is software that runs on the Content Provider’s server, and has access to the usage data. Library Content Provider ERM SUSHI Client Internet SUSHI Server (web service) Usage Data When the ERM system wants a COUNTER report, it sends a request to the SUSHI client, which prepares the request. Library Content Provider ? ERM Request SUSHI Client Internet SUSHI Server (web service) Usage Data The SUSHI request is sent to the Content Provider. The request specifies the report and the library the report is for. Library Content Provider ? ERM Request SUSHI Client Request Internet SUSHI Server (web service) Usage Data The SUSHI server reads the request then processes the usage data. Library Content Provider ? ERM Request SUSHI Client Internet SUSHI Server (web service) Usage Data The SUSHI server creates the requested COUNTER report in XML format. Library Content Provider ? ERM SUSHI Client Internet SUSHI Server (web service) COUNTER Usage Data A response message is prepared according to the SUSHI XML schema. Library Content Provider ? ERM Response SUSHI Client Internet SUSHI Server (web service) COUNTER Usage Data The COUNTER report (XML) is added to the Response as its payload. The response is sent to the client. Library Content Provider ? ERM Response SUSHI Client Internet SUSHI Server (web service) COUNTER Usage Data The COUNTER report (XML) is added to the Response as its payload. The response is sent to the client. Library Content Provider ? ERM Response SUSHICOUNTER Client Internet SUSHI Server (web service) Usage Data The SUSHI client processes the response and extracts the COUNTER report. Library Content Provider ? ERM Response SUSHICOUNTER Client Internet SUSHI Server (web service) Usage Data The extracted COUNTER report is passed to the ERM system for further processing. Library Content Provider ERM COUNTER SUSHI Client Internet SUSHI Server (web service) Usage Data SUSHI: Status of Z39.93 200x • Trial period ended in May 2007 • Successful implementations • A few minor technical adjustments made • Revisions to the standard have been finalized • Currently at ballot Overview • Brief history of usage statistics for e-resources • ERM systems are well suited for usage statistics • Reporting potential of the ERM • Challenges faced for successful reporting • COUNTER • SUSHI • Looking ahead 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 Timeline – looking ahead … Online collections use grows… ICOLC Guidelines release 1 ICOLC Guidelines rel 2 COUNTER formed • Ballot closes early COUNTER COP release 1 September committee formed ERMIshould • With approval, SUSHI be a standard First commercial ERM released by the end of 2007 SUSHI committee formed COUNTER COP rel. 2 SUSHI as draft standard ICOLC endorses SUSHI COUNTER audit SUSHI released COUNTER SUSHI to be released as NISO Z39.93 COP rel 3 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999 1998 1997 1996 Timeline – looking ahead … Online collections use grows… ICOLC Guidelines release 1 ICOLC Guidelines rel 2 COUNTER formed COUNTER COP release 1 ERMI committee formed consortium • Introducing specific reports First commercial ERM released SUSHI committee formed •XML based COUNTER COP rel. 2 •One report with details for each member SUSHI as draft standard of the consortium ICOLC endorses SUSHI COUNTER audit • SUSHI support may become a requirement SUSHI released for COUNTER compliance. COUNTER COUNTER code of practice release 3 under consideration… COP rel 3 Looking ahead • COUNTER - Consortium reports - Updated schema - New metrics and reports • SUSHI can be expanded to harvest other data - Holdings (ONIX SOH) - License terms (ONIX PL) - Financial terms • Tools and services to assist with data normalization - E.g. XISBN, XISSN projects from OCLC SUSHI: Resources • 1999 ICOLC guidelines for usage statistics: http://www.clir.org/pubs/reports/pub94/appendixb.html • 2001 ICOLC Guidelines for Usage Statistics: http://www.library.yale.edu/consortia/2001webstats.htm • COUNTER Code of Practice web site: http://www.projectcounter.org/code_practice.html • SUSHI web site: http://www.niso.org/committees/sushi_com.html • ERMI DLF Report: http://www.diglib.org/standards/dlf-erm02.htm • NISO Newsline, Jan 2006: http://www.niso.org/news/newsline/NISONewslineJan2006.htm#Story3 • XISBN home page: http://www.worldcat.org/affiliate/webservices/xisbn/app.jsp SUSHI Thank you! Oliver Pesch opesch@ebsco.com
