- The most recent 'Making the Most of JUSP' workshop brought together a selection of attendees from different institutions - we were pleased to see people from a broad geographical spread, with different levels of experience with JUSP, and different types of roles within their institution:
JUSP at the University of Bath
- After everyone had introduced themselves, the day began with our first presentation which was from our host, Kevin Sanders at University of Bath. Kevin began by sharing that he uses JUSP quite a lot but in a basic way so would like to learn more about how to use it. The main use for University of Bath is regularly gathering the JR1 and JR1a information to enable subject librarians to understand what resources users are accessing to inform future purchasing decisions.
- Kevin still has to collect data from some publishers whose data is not in JUSP - this can be a time consuming process to visit each of the different sites and get data from there, and sometimes there are issues with individual publishers which can delay the process. There can also sometimes be mistakes due to repetition and human error. Before JUSP, this was the process for all publishers, so Kevin was pleased to highlight that "JUSP saves so much time and makes it a less strenuous task".
- Once Kevin has collected the usage statistics for each of the relevant publishers, these are shared via an intranet which subject librarians can access. This stores an archive of the data from JUSP (in addition to other data such as that from KB+). Kevin highlighted that the downside to archiving data rather than using linked data is that it won't be updated if there are any changes (e.g. corrections in data from publishers). He is keen to used linked data in future.
- In addition to this use of JUSP data, Kevin also plans to use the titles and deals reports to inform decision making and collection management; the publisher and gateway statistics for usage trends; and the usage profiling reports to see if there are any trends emerging beyond the institution. In addition, University of Bath has a Research Services department who would like to look at JR1 GOA information in future.
- Kevin's wish list for using JUSP data in future included the following items:- Linked data rather than archiving- Including more publishers in JUSP- Mixed methods analysis of usage data
- Kevin is keen to continue to support community-based collaborative tools like JUSP, and ended with a great quote about why he likes JUSP:
- Kevin's full presentation is available to view on Prezi:
Discussion and workshop activities
- After Kevin's presentation it was time for a discussion about JUSP use - how it was currently being used by attendees, and how people would like to use it. As we had a varied mix of attendees, the current usage and frequency of use of JUSP varied. However, a few key themes came out of the discussion:
- Positive feedback was given on some of the reports within JUSP (e.g. trends) and the fact JUSP is not supplier led and is therefore neutral. Fortunately, much of the 'What we'd like to see from the future' items were things the JUSP team are also keen to progress, many of which are already being planned (more on this later as this was covered in the afternoon session). Some interesting new suggestions included functionality to look at subject specific journals (e.g. for subject librarians to mark up titles to view JUSP data within their area of responsibility), and offering guidance and support for use of JUSP by other staff in the library (i.e. those who may use the data to inform decisions, rather than those who collate the data).
- We then had some practical exercises which attendees worked through using the JUSP demonstrator data. The current set of workshop exercises will be available on the JUSP website shortly - the previous set of workshop exercises (and answers) are available for use at the bottom of the Events and Training section of the JUSP website:
- The morning exercises focused on journal level reports (i.e. JR1, JR1a, JR1 GOA), summary reports (i.e. trends, SCONUL return, use of gateways and host intermediaries, usage ranges), and tracking individual titles.
- After the exercises, sharing the answers, and discussing potential uses of these reports within attendee's institutions, it was time for a well-deserved lunch break where attendees had the opportunity to chat about their roles, responsibilities, and some of their current projects - these sorts of events are always useful for getting people together to share experiences.
- Once everyone was fully energised, the afternoon session kicked off with a couple of presentations about interoperability of JUSP i.e. how it can work with other systems. Firstly, we had a presentation from Damyanti Patel, Data Manager for Jisc Knowledge Base+.
- Knowledge Base+ (KB+) is a Jisc shared service for libraries which incorporates information on:- Publications (i.e. packages, titles, platforms, coverage)- Subscriptions (i.e. entitlements, renewals, link resolvers, usage statistics)- Licences (i.e. creating, storing and managing licences)It also incorporates community and collaboration functionality such as the ability to add documents and notes; receive announcements; and participate in discussions.KB+ is a relatively new service available as part of the core Jisc service to institutions. Damyanti highlighted that different institutions are using it in different ways, and one of the main features of KB+ is the flexibility in how it can be used to suit different types of institutions and different workflows. One example she gave is simply using KB+ as a repository for licences. In this way, it enables shared access to the licenses in a standard format to make it easier to understand. NESLI licences are added by KB+ data managers, which institutions can copy so they have the details, and can then edit if necessary. Institutions can also add a scanned copy of the signed licence, as well as any notes or further information.Damyanti closed her presentation by talking about the interoperability between KB+ and JUSP, and how you can view usage statistics from within KB+. There is a user guide on this topic from the KB+ blog: