PRIMO AT THE ROYAL LIBRARY OF DENMARK Integrated search – Google of the library ?

1. PRIMO AT THE ROYAL LIBRARY OF DENMARK Integratedsearch – Google of the library? Helsinki, October 28 2010

2. Primo at RLD | Helsinki, October 28 2010 • Agenda • Background:The Primo Consortium • Background: CULIS consolidation • Primo implementation at the Royal Library • Usabilitytesting and userresponse • Impact of the CULIS consolidationproject • Upgrading to Primo version 3 – firstimpressions • Pros and cons of the consortia model • Primo strategy for the near future • The Royal Library long term strategy

3. Primo at RLD | Helsinki, October 28 2010 • The Primo consortia in Denmark • The Administrative Library • Technical Information Center of Denmark • The Royal Library • Aalborg University Library • Primo consortiaformed in 2007 • Formal organization • Three live Primo sites

4. Primo at RLD | Helsinki, October 28 2010 • CULIS consolidation • Joint library organization of Copenhagen University libraries and RLD • Technical project following the formation of CULIS • All faculty- and department libraries and RLD • Joint Aleph, Primo, SFX and DADS solution • Merging 43 separate ALEPH solutions into 1 • 17 lending libraries with different policies • Planned and completed 2008-2009 • Extensive policies og procedures • 75 collections, 50 locations and branches

5. Primo at RLD | Helsinki, October 28 2010 Primo at the Royal Library ALEPH version 16 OPAC

6. Primo at RLD | Helsinki, October 28 2010 Primo at the Royal Library Primo version 2

7. Primo at RLD | Helsinki, October 28 2010 • Primo at the Royal Library • System implementation 2007 • RLD working towards launch in 2008 Aleph, SFX and DADS article search integration • Beta version September 11 2008 4,7 mio. catalog records + 40 mio. article records • 2009 expansion due to CULIS consolidation • More records, many collections and branches • Production March 11 2009 6,2 mio catalog records, 40 mio article records

8. Primo at RLD | Helsinki, October 28 2010 • Usabilitytesting of Primo in 2008 • Handled in 2008 by a professional usabilitycompany • 11 test subjectstestedindividually for 90 minutes. (5 students, 3 ph.d students and 3 scientists) • Positive: • Clear indication of ressource types • Veryuseful option to limit results (facets) • Access to articlesearch • Easy navigation and functionality • Search of unexpectedresourceswas a positive surprise (discoveryaspect) • Negative: • Articlesearchtoohard to find (separate tab) • Toodifficult to getfulltextaccess. (SFX) • Toomanylibrary terms on the interface • Advancedsearch not advancedenough

9. Primo at RLD | Helsinki, October 28 2010 • Recommendations of the usability test • Resources: clear definition of content and coverage of resources • Library terms: removedortranslated to commonlanguage • Contextualhelp: relevant helpwhereneeded • Request and access: must besimplified and cleared of organizationalissues • Search options: focusonboth ’Googleusers’ and advancedusers • Integratedsearch: aim for real integration – one interface, onesearch, oneresult set • Social technologies: onlyusewhere relevant and of real value to the users

10. Primo at RLD | Helsinki, October 28 2010 • Impact of the CULIS consolidationproject • Groundbreakingproject and cooperationbetween UC and RLD • Momentum wascritical – compromisewas the key • Technical solution to organizationalissues • The Primo integration was an overall success … but • Reflectscomplexity and flaws of the data layer • Many policy and functionalitydiscussions • Knowyourcustomer! Knowyourstrategy! • ”The best is the good’sworstenemy”

11. Primo at RLD | Helsinki, October 28 2010 • Upgrading to Primo version 3 – firstimpressions • Upgrade summer 2010 • Beta september – Live October 18

12. Primo at RLD | Helsinki, October 28 2010 • Upgrading to Primo version 3 – firstimpressions • Seamless integration withAlephlogistics – almost • Better integration with SFX link resolver • Improved interface look and feel – farewell to pop ups • More open platform – easier to integratethird party functionality • Semi-intelligent feedback onuser options in specificcontext

13. Primo at RLD | Helsinki, October 28 2010 • The consortia model • Expectations: • The economical motivation – Licensing, maintenance, total cost of ownership • The potential for collaboration, exchange of work and ideas • The reality: • Shared Primo system covering multiple Aleph solutions • Requiresclosecollaboration and crossconsortiadecissions • Requires a real activeconsortiaorganization • Requires a consortia ’owner’ and clear definition af responsibility • Requiresconstantfocuson actions and consequenses • Not suitable for individual and equal institutions - withdifferentproirities

14. Primo at RLD | Helsinki, October 28 2010 • Primo strategy for the near future • Additionalsearch options (MARC recordview, push to externalsearchengines) • Third party integration (reference tools, mobile devices, social networks) • Formalized design and terminologypolicies • Complete new usability test with clear userprofiles • Focusonusersatisfaction and fulfillment • Bewhere the usersare, on the users terms

15. Primo at RLD | Helsinki, October 28 2010 • The Royal Library long term Primo strategy • Harmonize and standardizeour data foundation • Standardize and simplifyourlogistics and policies • In principleachieve system independence • Increasingfocuson total cost of ownership • Constantviewonlicensing, maintenancecost, automatedwork flows • Primo as an exploratorysearchtool • Primo as one stop search for all resources • Fulltexts, images, maps, digital culturalheritage

16. Primo at RLD | Helsinki, October 28 2010 • Questions? • Royal Library Primo version 3: • http://rex.kb.dk • Ole Holm • Head of Library Service • The Royal Library, Copenhagen • oho@kb.dk