1 / 30

JURO : Creating the Journal Usage Report Online System

Explore JURO, an open-source software for capturing and analyzing journal usage data to support library administration and decision-making. Learn about its features, benefits, and implementation timeline.

kasperj
Download Presentation

JURO : Creating the Journal Usage Report Online System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 6th Annual Hong Kong Innovative Users Group Meeting8-9 December 2005, Hong Kong JURO : Creating the Journal Usage Report Online System Presented by Ki Tat LAM Head of Library Systems The Hong Kong University of Science and Technology Library lblkt@ust.hk

  2. Contents • What is JURO and Why to use JURO? • Project COUNTER • JURO system architecture and design • Using JURO • Thoughts and future developments • Conclusion

  3. What is JURO? • JURO – Journal Usage Report Online – is an open source software thatenables libraries to: • capture journal usage data from COUNTER-compliant usage reports and in-house usage statistics • link the bibliographic, order and holdings records from library catalog with usage data • query and generate different usage reports based on the user preferences • preserve usage data for long-term use

  4. Why JURO? • Library administration, collection development and reference staff need to have a better understanding of how the subscribed resources are being used • Frustrated by the poorly organized usage data • Different ways of recording and interpreting • In varying formats – Excel, Web page, etc. • Scattered sources from vendors and in-house • Failure of linking to bib/order/holdings records in library catalog for analysis

  5. Why JURO? [cont.] • Demand to have better control of usage statistics is accelerated by the proliferation of electronic resources, particularly e-journals • As Josephine Tsui (our Collection Development Manager) expressed: we need a system that can help us to: • Determine what electronic journal titles are to be swapped towards the end of the year

  6. Why JURO? [cont.] • Aid cancellation decision by • Comparing usage statistics of print and electronic versions • Reviewing usage statistics of print only journals • Conduct collection analysis on usage by call number • Trace normal usage patterns against statistics supplied by the vendors

  7. Implementation Timeline • June 2005 - Funding available to hire temporary programmers for a few months for systems-related projects • August 2005 – Began JURO system design and software programming by: • Lawrence Chan, Ho Wing Kee and Allen Lam, with valuable help on ideas, testing and evaluation from colleagues from Collection Development and Acquisitions • November 2005 – Released JURO Version 1.0

  8. Project . • Counting Online Usage of Networked Electronic Resources [http://www.projectcounter.org/] • “An international initiative designed to serve librarians, publishers and intermediaries by facilitating the recording and exchange of online usage statistics” • Launched in March 2002

  9. Project COUNTER [cont.] • 47 COUNTER-compliant vendors so far (as of November 2005) • Includes almost all major vendors we subscribe to – 26 of them have been configured in JURO • Such as: ACS, Blackwell, EBSCO, Elsevier, Emerald, Extenza, HighWire, Ingenta, Kluwer, ProQuest, Springer, Scitation-AIP, Taylor & Francis, Thomson, Wiley, etc. [http://www.projectcounter.org/articles.html]

  10. Project COUNTER [cont.] • Produces Code of Practice so that the use of electronic resources can be measured in a more consistent way • COUNTER Code of Practice for Journals and Databases • Release 1 – January 2003 • Release 2 – April 2005 • COUNTER Code of Practice for Books and Reference Works • Draft Release 1 – January 2005

  11. Project COUNTER [cont.] • Major Types of Reports: • Journal Report 1: Number of Successful Full-Text Article Requests by Month and Journal • Journal Report 2: Turnaways by Month and Journal • Database Report 1: Total Searches and Sessions by Month and Database • Database Report 2: Turnaways by Month and Database • Database Report 3: Total Searches and Sessions by Month and Service

  12. Sample COUNTER-compliant usage report provide from vendor [JR1_FullTextArticleRequests_10023722_Institution.csv]

  13. COUNTERUsage Files In-HouseUsage Files (e.g. print journalsaccess survey) Usage Data Bib/Order/HoldingsData LibraryCatalog JURO System Web-based Querying and Report Generation JURO System Architecture

  14. JURO System Requirement • Platform – Java programs, MySQL database, Tomcat with web servlets • Can be run on Linux or Windows • Open source software – contribution of source codes and feedback are welcomed • Developed based on INNOPAC; JURO will function without bibliographic, order and holdings data, or they can be imported from any other systems

  15. Figure 1. JURO’sWeb-based client interface showing theCreate UsageReport form

  16. Figure 2. You can select the following types of reports, by year or by month Figure 3. You can limit or filter the result sets by a range or by keywords in Boolean

  17. Figure 4. You can select what fields to display in the report

  18. Hyperlink to record in INNOPAC Buttons for sorting Figure 5. Full-Text Access to Wiley e-journal titles

  19. Figure 6. Print Journal Usage Report for 2005 sorted by call number

  20. Figure 7. Print journals access statistics showing a significant decrease of usage over the years

  21. Figure 8. Displaying print and electronic journal titles in parallel for usage analysis

  22. Figure 9. Rankinge-journal usage of 2004/05, with the top 15 titles

  23. Possible error from vendor! Figure 10. Identifying possible discrepancies in statistics provided by vendors by tracing the usage patterns

  24. Import of Usage and Bib Data • Import of COUNTER usage data is tedious and time consuming – requiring downloading the files vendor by vendor and month by month • There is an initiative to enable the transfer of usage data via web services - SUSHI (Standardized Usage Statistics Harvesting Initiative) • 22 November 2005 – Swets successfully tested the transfer to Innovative and Ex Libris based on the SUSHI protocol

  25. Import of Usage and Bib Data [cont.] • SUSHI protocol will be issued as a NISO standard in early 2006 • Import of bibliographic, order and holdings information from INNOPAC/Millennium is cumbersome – requiring creation of review lists and exporting the data elements • How well Millennium ERM module integrates COUNTER usage data has yet to be seen • Suggestion to Innovative – to enhance its web services product to allow remote function calls to create and output review lists.

  26. Open Source Software • JURO is open source software using the GNU Public License • Available for download from: http://library.ust.hk/software/juro.html • We believe that it is highly beneficial that libraries which develop non-commercial software tools which might prove useful to other institutions make their efforts available to the larger community of libraries

  27. Future Enhancements • Closely watch the development of SUSHI and will incorporate it to JURO as soon as vendors are ready for it • Improve the client interface – based on feedback from users (from HKUST and other institutions that adopt JURO) • Incorporate more types of reports • a challenge to capture usage data from web access logs for access scripted URLs

  28. Conclusion • JURO is software to acquire electronic resource usage statistics from vendors and in-house, and allow online querying and generation of usage reports • It meets a clearly defined need not yet being met by available software • Uses COUNTER-compliant usage data • Consolidates multiple partially duplicative efforts by different library units

  29. Conclusion [cont.] • Permits much more accurate analysis for Collection Development and Acquisitions efforts • Semi-integrated with INNOPAC, the library catalog • More importantly, JURO is an open source software package that allows more institutions to use it and expand on its features

  30. Thank You!

More Related