HIKE Project Overview

1. Jisc HIKE workshop 26 February 2013 HIKE Project Overview Graham Stone Dave Pattern Amy Devenney #JiscHIKE http://eprints.hud.ac.uk/16837 This work is licensed under a Creative Commons Attribution 3.0 Unported License

2. Project targetsOr at least what we said we’d do back in June! • We said the project would be a success if: • Data is successfully loaded and interoperability between systems is achieved • An evaluation of both KB+ and Intota are undertaken on behalf of UK HE • Recommendations on platform development are proposed and adopted as part of the future development plans for Intota, KB+ and commercial systems • Suitable workflows and efficiencies are highlighted in a toolkit

3. Project Blog http://library.hud.ac.uk/blogs/projects/hike/

4. WorkflowsLooking for known knowns! Before we can know what we want from a web-scale management system we need to understand the workflows we have in place for the current LMS and related systems Once we have established the problems and frustrations library staff and users feel we can identify what we expect from the new systems, such as Intota, and where they can improve on the older models

5. WorkflowsE-resources • Mapped e-resource workflows as part of the ‘Shared ERM requirements project’… • …which became KB+

6. WorkflowsE-resources • Mapped e-resource workflows as part of the ‘Shared ERM requirements project’… • …which became KB+

7. WorkflowsE-resources TERMS: Techniques for Electronic Resource Management http://library.hud.ac.uk/wikiterms/Main_Page

8. WorkflowsAcquisitions • Ordering processes • DawsonEnter workflow • eBook workflow • Suppliers within the National Book contract • Suppliers outside the National Book contract

9. WorkflowsVertical analysis showing complexity Based on the Effective Systems Design and Requirements Analysis: the ETHICS Approach by Enid Mumford • Checking and amending orders from the Subject teams before sending them to the suppliers • Problem prevention/solution activities – identify problems which must be prevented or quickly and easily solved (what we don’t want to happen) • Co-ordination activities – identify the activities that are co-ordinated within the department and those which are co-ordinated with other systems/departments • Development activities – identify products, services, etc. which need to be developed/ improved. • Control activities – identify how the department is controlled to ensure it works efficiently and meets its targets

10. WorkflowsLooking for efficiencies • A new system would have to: • Streamline the ordering processes • Reduce the number of systems used and creating efficiencies while ordering • Create efficiencies in the initial ordering process • Reduce delays in order to shelf time • Provide instant access to e-books • Provide improved reporting features on the acquisitions module

11. WorkflowsAnalysis of the financial process http://www.flickr.com/photos/donsolo/4953529480/ Inability of Agresso and LMS to integrate A “financial danger zone” ! Streamlining the payment process Compatibility with eMarketplace?

12. The ideal workflow?Under construction http://www.flickr.com/photos/lou/1353616104/

13. KnowledgeBase+Testing • We have done lots of user testing! • Licences • Core subscriptions • Big deal renewals • Compared KB+ with 360 Resources Manager • Aims and objectives of the 2 systems • Population of the 2 systems • Functionality of the 2 systems

14. KnowledgeBase+/Resource ManagerComparison • To understand how the systems will help us with our workflows • To access the appropriateness of each resource • We recommend adding data to KB+ first – others may disagree • We see KB+ as an ideal reference tool for licensing questions e.g. for subject teams and enquiries • Reference Manager is more interactive and suitable for the e-resources team • Provided recommendations for further developments to both

15. Change managementA possible risk The adoption of either KB+ or Intota would undoubtedly bring about a change within the library environment in which they are adopted We need all members of staff to be behind the idea if something as big as this is going to work!

16. Change managementAn excuse for coffee and cake! “In ensuring that relationships within the team are trusting and solid, communication channels are open both ways and staff are completely involved in and informed about the project it is hoped staff will support and feel comfortable with the change created enhanced job satisfaction which in turn will create a more efficient organisation” http://www.flickr.com/photos/becca_ca_ca/4866640594/

17. IntotaSome initial thoughts and more to do! • We’ve spoken to Dawson about their role in Intota • We’ve held initial talks with Swets • We’ve discussed possible APIs that would be needed to talk to other systems • Agresso (finance), ASIS (student records), MyReading (reading list software), Sconul, Library Analytics, British Library…

18. The likely end point…or start point! • An old “JISC” style final report • The blog posts in a logical order • Write-up of this workshop • Summary of recommendations to KB+, Serials Solutions and Jisc • A web scale management solution specification document! • Possible collaboration • Using the case studies as a starting point?

19. Any Questions? http://www.flickr.com/photos/bnilsen/3894005/

20. This afternoon…or how to keep you all awake • We want to hear from you! • 3 group activities! • Discussion around workflows • Discussion around cultural change • Discussion around the different types of supplier data & APIs needed