1 JURO4C: Online Usage Reports for Consortia José Fernandes 12th October 2006

2 Agenda  Introduction  Project focus  Methodological approach  JURO  JURO4C - JURO for Consortia  Conclusions and Future Work

3 Introduction b-on is the acronym for Biblioteca do Conhecimento Online, (Online Knowledge Library), established in March 2004  it started with 48 members, got 69 in 2005, and has grown to 74 in  18 are universities, 22 polytechnics, 13 research institutes, 3 non- profit organizations, 8 governmental institutions and 9 hospitals  It serves more than de users  In 2004 b-on provided access to 3500 electronic journals. Since 2005 this number raised to more than full text journals for hospitals and for the other institutions  b-on subscribes 15 publishers, 8 of them are COUNTER compliant

4 Project focus Content providers make available data regarding the usage of the subscribed titles. This is key to assess the resources value to the community. This information allows to: - optimize content provisioning, - improve the negotiation process, - prepare better communication and, - dissemination The usage data provided by publishers, in most cases, does not follow a known format (COUNTER) or standard and it becomes difficult to process the information. This makes it very difficult to have reliable usage statistics.

5 Methodological approach With this in mind, a prospective analysis was performed to find out which solutions were available and what could be used to do the job. Three possible solutions were identified : 1.purchase of an ERMS to manage online collections, The time required to have a fully functional ERMS would be too long to be considered in a short term. It would not solve the problem of non COUNTER compliant reports from publishers. 2.outsourcing to a company (in this case MPS Scholarly Stats) that would be responsible for collecting usage data, standardize it and store it on a central repository and provide members with reports. This proved to be very expensive

6 Three possible solutions were identified (cont…): 3.develop a custom made application A good starting point for this application is an open source application named JURO, developed by The Library of the University of Science and Technology of Hong Kong This was the adopted solution: build a custom made application called JURO4C (JURO for Consortia) that would meet a set requirements Methodological approach

7 JURO JURO is an open source platform that allows libraries to: Capture journal usage from two sources: COUNTER compliant usage reports and in-house journal usage; Link up the bibliographic, check-in and order records in the library catalogue with those two journal usage sources; Generate different usage statistical reports based on the user preferences; Preserve usage statistical data for long term use. Although it was designed with COUNTER compliant source files, it also works with non-COUNTER compliant input files.

8 The user will be able to generate Counter Compliant JR1 Reports and filter the data according to specified criteria: - Most used journals; - Less used Journals; - Access data filtered by date; - Access data filtered by platform; - Combination of criteria (filtering data by platform, journal and date) This allows for comparisons between publishers, journals and periods of time. For more information please go to JURO

9 JURO4C JURO4C: intends to extend JURO’s capabilities for Consortia The main goals of JURO4C: Support for Consortia Extended data management Extended Filtering and Reporting Knowledge base management

10 JURO4C On top of doing all what JURO does, JURO4C has to meet some functional requirements: Support for ConsortiaSupport for Consortia –Introduce the concept of institution and consortia (for data gathering, consolidation, storage and reporting) –Manage multi-user and user profiles Extended data managementExtended data management –Data neutralization –Data preservation Extended filtering and ReportingExtended filtering and Reporting –More criteria to filter and sort the usage data –Generate more reports; –Data export; Knowledge base managementKnowledge base management –Develop an interface for managing (adding, editing and deleting) publishers/platforms in a more friendly way;

11 JURO4C Features already implemented:  Support for institution type  Support for institutions and departments  JR1* reports (Full-Text Article Request by month and Journal)  Average usage by platform  Totals by platform  Filter by date and platform

12 Institution types

13 Number of FTE Institution type Support for departments in consortia Institutions

14 Import & Consolidate

15 Report selection form Available reports Grouping options Filter options

16 Counter – Journal Report 1 Grouping options Sort options

17 Other reports

18 Future work Finish the implementation phase –Support for different access levels –Support for consortia and departments –Finish the reports –Documentation and manuals –Develop XML services for integration Put pressure on the publishers to: –Be compliant with the counter standard –Be compliant with SUSHI when they are counter compliant –Supply statistics by institution and department Follow the developments on: –SUSHI –ERMS

19 Any question?