Published on

This presentation illustrates an online A-Z usage statistics web site at Arizona State University Libraries and how usage reports are gathered, stored and made accessible to decision makers. Furthermore, details about creating a usage web site and challenges one may encounter. Additionally, potential uses and future plans are discussed.

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. Creating and Maximizing the Use of Usage Stats Smita Joshipura & James Carvalho ER& L Conference UCLA February, 2009
  2. 2. Goals <ul><li>Step-by-step process for creating a static online Usage Web Site </li></ul><ul><li>Maximizing use of this Web Site </li></ul>
  3. 3. Presentation Outline <ul><li>Arizona State University </li></ul><ul><li>Electronic Usage Stats overview </li></ul><ul><li>Need for Usage Stats at ASU </li></ul><ul><li>A-Z Usage Stats Web Site at ASU </li></ul><ul><li>Steps for Creating A-Z Usage Stats Web Site </li></ul><ul><li>Use of the Web Site for Decision Making </li></ul><ul><li>User Survey of the Web Site </li></ul><ul><li>Future Plans & Challenges </li></ul>
  4. 4. Arizona State University : One University in Many Places <ul><li>One of the largest higher educational institutions in the USA </li></ul><ul><li>4 campuses: </li></ul><ul><li>Tempe, West, Polytechnic & Downtown Phoenix </li></ul>
  5. 5. Arizona State University Libraries : One Library in Many Places <ul><li>Branch libraries: 8 </li></ul><ul><li>ASU at the Tempe campus </li></ul><ul><ul><li>Architecture & Environmental Design Library </li></ul></ul><ul><ul><li>Hayden Library </li></ul></ul><ul><ul><li>Law Library </li></ul></ul><ul><ul><li>Music Library </li></ul></ul><ul><ul><li>Noble Science & Engineering Library </li></ul></ul>
  6. 6. Arizona State University Libraries : One Library in Many Places <ul><li>ASU at the West campus </li></ul><ul><ul><ul><li>Fletcher Library </li></ul></ul></ul><ul><li>ASU at the Polytechnic campus </li></ul><ul><ul><ul><li>Polytechnic Library </li></ul></ul></ul><ul><li>ASU at the Downtown Phoenix campus </li></ul><ul><ul><ul><li>Downtown campus Library </li></ul></ul></ul>
  7. 7. FTE Enrollment at ASU : Fall 2008 Tempe campus 46,595 West campus 7,694 Polytechnic campus 5,271 Downtown Phoenix campus 4,451 Total 64,011
  8. 8. ASU Libraries : E-Resources Collection (2006-07) <ul><li>Databases: 400+ </li></ul><ul><li>E-Journals: 61,986 </li></ul><ul><li>E-Books: 291,426 </li></ul>
  9. 9. Electronic Usage Stats <ul><li>Process of collecting and disseminating usage data: Time-consuming, tedious, challenging </li></ul><ul><li>Process extremely helpful, can not be ignored </li></ul><ul><li>Timely, consistent and accurate usage data: critical for selectors </li></ul><ul><li>Very practical and informative tool to assist librarians in collection development decisions (selection & retention) </li></ul>
  10. 10. Electronic Usage Stats : Initiatives <ul><li>ARL’s E-Metrics project : Measures for E-Resources </li></ul><ul><li>ICOLC Guidelines for Statistical Measures of usage of Web-based Information Resources : Developed set of guidelines to measure usage stats </li></ul>
  11. 11. Electronic Usage Stats : Initiatives <ul><li>COUNTER - Counting Online Usage of NeTworked </li></ul><ul><li>E-Resources (2002) : Code of practice for measuring consistent and reliable data </li></ul><ul><li> </li></ul><ul><li>SUSHI - Standardized Usage Statistics Harvesting Initiative : Protocol for automatic harvesting of stats in ERM </li></ul><ul><li> </li></ul>
  12. 12. Need for Usage Stats at ASU <ul><li>Substantial collection of E-Resources </li></ul><ul><li>Prominent role in evaluation of E-Resources by Collection Steering Council </li></ul><ul><li>Assists with timely collection development decisions </li></ul><ul><li>Implementation of Web Site in 2007 </li></ul>
  13. 13. A - Z Usage Stats Web Site at ASU <ul><li>Started with 200 items (packages and titles) </li></ul><ul><li>Current site : 370 items </li></ul><ul><li>Identifies COUNTER compliant items </li></ul>
  14. 14. Step #1 : Compile Necessary Info for Obtaining the Usage Reports <ul><li>Vendor/Publisher/Provider </li></ul><ul><li>Storage Directory </li></ul><ul><li>Resource Type </li></ul><ul><li>COUNTER Compliant </li></ul><ul><li>Web Site URL </li></ul><ul><li>User Id </li></ul><ul><li>Password </li></ul><ul><li>Contact </li></ul><ul><li>Status </li></ul>
  15. 15. Step #2 : Decide on a Naming Convention for the Usage Reports <ul><li>For example: </li></ul><ul><li>2008Jn1-ArticleRequests.xls for Journal Report 1 </li></ul><ul><li>2008Db1-DbSearchesSessions.xls for Database Report1 </li></ul><ul><li>2008Bk1-TitleRequests.xls for Book Report 1 </li></ul><ul><li>2008Usage.xls or 2008Usage.html or more descriptive names for non-COUNTER reports </li></ul>
  16. 16. Step # 3 : Create Local Directories and Sub-Directories <ul><li>Create 3 main directories such as Journals, Databases and E-Books for COUNTER reports </li></ul><ul><li>Create another for non-COUNTER reports </li></ul><ul><li>Create appropriate sub-directories under each </li></ul>
  17. 17. Step # 4 : Gather and Store Usage Reports <ul><li>Gather reports from provider </li></ul><ul><li>Save them to the sub-directories as discussed in </li></ul><ul><li>step # 3 </li></ul><ul><li>Use the names as discussed in step # 2 </li></ul>
  18. 18. Step # 5 : Create and Copy Menu Page to Each Storage Directory <ul><li>Create 4 types of “index.html” with links to the various usage reports </li></ul><ul><li>Copy each to appropriate set of sub-directories. </li></ul><ul><li>Process for copying: </li></ul><ul><ul><li>Generate directory list </li></ul></ul><ul><ul><li>(e.g. ListDirNames.bat with dir /a:d /b > dir.txt) </li></ul></ul><ul><ul><li>Copy index.html to appropraite directories </li></ul></ul><ul><ul><li>e.g. CopyFileToDir.bat with: </li></ul></ul><ul><ul><ul><li>copy index.html sub-directory1 </li></ul></ul></ul><ul><ul><ul><li>copy index.html sub-directory2 </li></ul></ul></ul>
  19. 19. Journals Menu
  20. 20. Step # 6 : Create an A - Z Menu Page to the Web Site <ul><li>Begin with a bare bones HTML page (index.html) i.e. just the header and footer </li></ul><ul><li>In Excel create the body portion of the HTML page </li></ul><ul><li>Copy and paste the body portion into index.html. </li></ul>
  21. 21. Body Portion of Index Page
  22. 22. Step # 7 : Transfer Reports to the Web Server <ul><li>Transfer all sub-directories </li></ul><ul><li>Transfer main index.html file </li></ul>
  23. 23. Usage Web Site
  24. 24. Tools <ul><li>Minimum tools required: </li></ul><ul><li>Excel </li></ul><ul><li>Notepad </li></ul><ul><li>Secure FTP (optional) </li></ul>
  25. 25. Web Site Challenges <ul><li>Obtaining current list of licensed packages and titles </li></ul><ul><li>Locating provider contact </li></ul><ul><li>Re-designating person for receiving usage reports </li></ul><ul><li>Requesting usage reports or log in information to provider usage web site </li></ul><ul><li>Generating separate usage reports (FT, searches & sessions) for individual databases </li></ul><ul><li>Creating Excel reports from CSV or Tab-delimited files </li></ul><ul><li>Generating usage reports from web logs </li></ul>
  26. 26. Use of the Web Site for Decision Making <ul><li>Usage Stats: An important criterion in analyzing </li></ul><ul><li>E-Resources </li></ul><ul><li>Other criteria such as price, interface, content overlap, technology, curriculum need, etc. </li></ul><ul><li>Utilized for Collection Realignment Project </li></ul>
  27. 27. User Survey on Usage Web Site <ul><li>Recently conducted a short survey </li></ul>
  28. 28. User Survey Results <ul><li>50% - Response rate </li></ul><ul><li>100% - Used the tool </li></ul><ul><li>100% - Serves as a valuable assessment tool </li></ul><ul><li>100% - Assists in timely collection development decision making process </li></ul><ul><li>57% - Data adequate </li></ul><ul><li>43% - Data not adequate </li></ul>
  29. 29. User Survey : Feedback <ul><li>Explicit definitions for non COUNTER compliant resources </li></ul><ul><li>Requires regular updates of data, cost information </li></ul><ul><li>Organization of data in HTML format </li></ul><ul><li>Host in ERM </li></ul>
  30. 30. Future Plans and Challenges <ul><li>ERM implemented in March, 2008 with Resource and Contact information </li></ul><ul><li>Coverage, Usage, and License information - Second phase </li></ul><ul><li>Not all providers COUNTER complaint (about 60%) </li></ul><ul><li>Manual process in ERM: Usage data requires conversion from non-XML to XML format </li></ul><ul><li>Few SUSHI complaint providers </li></ul>
  31. 31. Questions ? ? ? <ul><li>Do you have any questions? </li></ul><ul><li>Do you have any comment, feedback? </li></ul>
  32. 32. Thank You  <ul><li>Smita Joshipura : [email_address] </li></ul><ul><li>James Carvalho : [email_address] </li></ul>