Enhancing life-long learning, teaching and research through information resources and services

1. Enhancing life-long learning, teaching and research through information resources and services

2. Working as a MetaLib tester and a Verde implementation partner Dr Richard Cross, eServices Manager (Resource Discovery) Libraries and Learning Resources, Nottingham Trent University

3. Agenda • Pre-release testing of MetaLib v.4.0 (December 2006) • Working as an ‘implementation partner’ for Verde v.2 (June 2007-) • Benefits, costs and caveats of partnership working

4. Pre-release testing of MetaLib v.4.0

5. Background and context • At Stockholm IGELU conference, September 2006, idea raised • IGELU and ELUNA participation in last-phase testing of MetaLib 4.0 • Following agreement: a very short period for preparation on all sides; degree of novelty in the process • ELUNA and IGELU advertised for testers • Two sets of testers; each working on product testing for one week • Based at Ex Libris offices in Jerusalem; expenses met by Ex Libris • Required to participate in pre-testing conference calls and post-testing report writing and user group feedback • Four testers selected • IGELU: Richard Cross, NTU; Rui Francisco, b-On Consortia • ELUNA: Lori Jargo, Brown University; Licia Duncan, PSCE

6. Testing – mechanisms and processes • Testing took place in Jerusalem in December 2006 • Karen Groves (MetaLib Product Manager) and Hedva Scop (MetaLib Development Team) served as hosts • Kick-off meeting with the development team to scope out process • Responsive to areas of user interest, expertise, responsibility • Set out timetable for week; mechanics of the process • Testing was undertaken using a combination of methods • Script driven – detailed walkthroughs; testing new and existing functionality • Open ended scenario – experimenting with customisation, module settings • Exploratory – work through /M and /V sides of different process • Audited reporting of ‘bugs’ through proprietary Test Director • ‘Verified fixed’ (QA confirms resolved) • ‘Closed’ (either ‘Rejected’ or reported as a ‘Duplicate’) • ‘Deferred’ (resolution suspended)

7. Testing – the customer-tester experience • Wide range of MetaLib v.4.0 functionality tested • /V – clustered / faceted searching; customisation; usability • /M – category management and IRD enhancements • System level – Upgrade Express • Testers were able to report ‘bugs’ – and see many of them fixed • Range of presentations were offered on v.4.0 developments • Opportunity to present to the MetaLib Development Team – not normally in contact with customers • Professional collaborative atmosphere throughout; nothing ‘off-limits’; encouragement to be open; to report and assess • Shared recognition of the utility of process for all involved

8. Post-testing follow-up • Participants prepared detailed reports for ELUNA and IGELU • Findings shared and discussed during conference calls • Agreed summary was submitted to Ex Libris – reaction to which was positive • Full reports were added to the secure members’ area of IGELU and ELUNA websites; summary freely accessible • Reports written for the user group press – inc SMUG-4-EU

9. Recommendations and observations To build on the positive experience it would be helpful to: • Clarify the status and remit of the testers and the testing process • Build-in lengthier preparation times – match workload to timeframe • Ensure full-breadth of functionality is tested – variety of methods • Explore combination of on-site and remote testing mechanisms • Integrate customer review of the implementation documentation • Maintain distinction between ‘bug’ reporting and ‘enhancement’ requests • Fully acknowledge differences between last-phase pre-release testing and involvement in the development process

10. Future developments • Shared recognition that this was an extremely productive first experience – this stopped it from being a ‘one-off’ experiment • Enthusiasm on user group side to repeat and to generalise across the Ex Libris product suite – already being used for ALEPH and other products • Important to manage expectations on both sides; build this process in to the product development lifecycle • Establishment of URM (Unified Resource Management) focus groups is a welcome expansion – customer input is being sought at the development and design stage • Very positive to see that the URM focus groups were over-subscribed – there are many active, interested, motivated customer sites out there!

11. Being a Verde implementation partner

12. Verde (for beginners…) • Ex Libris’ ERM (Electronic Resource Management) application • Designed to assist in the lifecycle management of electronic resources of all kinds (databases, ejournals, ebooks and more) • Works very closely with SFX and with ALEPH/Voyager • Enables you to store wide range of ERM data, share that data with other applications, report on that data, provide library colleagues with permission-controlled access to that data • Offers pre-configured ‘Workflows’ to walk you through Acquisitions and Licensing processes

13. Nottingham Trent University’s implementation • May 2006: Second global site (and first UK site) to take Verde 2.0 • July 2007: Extended implementation led to a phase one ‘go live’ • Began to act as a Verde ‘Reference site’ for potential Ex Libris customers • Autumn 2007 onwards: enriched Verde with ERM data (including Licence, Acquisition, Usage, Organisation records) • From 2008: efforts to ‘mainstream’ Verde in electronic resource management within LLR

14. Ex Libris and issues surrounding Verde 2.0 • Initially, Verde v.2 was a ‘troubled’ product • Ex Libris System Seminar – customer representatives meet senior product and company managers [May 2007] • Ex Libris announced urgent plan of action to stabilise and improve Verde • NTU was invited to work as one of four ‘implementation partner’ site [July 2007]

15. Implementation Partner status • An informal rather than a contractual relationship What does it involve? • Begins with two-day site visit from Verde product managers • Testing alpha and beta versions of upgrades, patches and fixes • Reviewing and commenting on documentation • Commenting on draft product announcements • Ties in with participation in IGeLU PWG and regular conference calls with product manager

16. Benefits of being an implementation partner? • Being one of the earliest voices that Ex Libris hears in response to its plans • Enjoying direct access to the product managers • Potential ability to influence and shape product development – hoping making that product better and more fit-for-purpose • Having early access to news about an evolving product

17. ‘Costs’ of being an implementation partner? • Despite being an informal relationship, still requires degree of commitment – to try out new software, to review, to report back • Ex Libris usually require feedback and testing reports within tight deadlines – sometimes with little advance notice • Does require a local staffing resource • Sense of responsibility to fairly present other customers of the product – might mean being interested in things that are not that important to your institution

18. ‘Caveats’ of being an implementation partner • Not all other customers may agree with your analysis and input – can be uncomfortable when feedback from others is critical • No guarantee that Ex Libris will accept and act on your feedback • Can be frustrating if Ex Libris do not give you feedback about your feedback • Ex Libris may decide to ‘do it anyway’ even if implementation partners and the Product Working Group oppose an idea • decision to stop developing Verde and to concentrate on URM was made despite just such opposition

19. Closing comments • One of the strengths of working with Ex Libris is the company’s recognition of the importance of the customer community and the willingness of the customer community to get involved • This is not the experience we at NTU have with all the software suppliers that we work with • Customers should encourage each other to contribute: • As product testers • As implementation and development partners • Through the national and international user groups

20. Thank you! Richard Cross, Nottingham Trent University richard.cross@ntu.ac.uk +44(0)115 848 4878