PRIMO AT THE ROYAL LIBRARY OF DENMARK Integrated search – Google of the library? Helsinki, October 28 2010

PRIMO AT THE ROYAL LIBRARY OF DENMARK

Integrated search – Google of the library?

Helsinki, October 28 2010

Primo at RLD | Helsinki, October 28 2010

Agenda

• Background: The Primo Consortium

• Background: CULIS consolidation

• Primo implementation at the Royal Library

• Usability testing and user response

• Impact of the CULIS consolidation project

• Upgrading to Primo version 3 – first impressions

• Pros and cons of the consortia model

• Primo strategy for the near future

• The Royal Library long term strategy

2


The Primo consortia in Denmark

• The Administrative Library

• Technical Information Center of Denmark

• The Royal Library

• Aalborg University Library

• Primo consortia formed in 2007

• Formal organization

• Three live Primo sites

3


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

4


Primo at the Royal Library

5

ALEPH version 16 OPAC



6

Primo version 2



• 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

7


Usability testing of Primo in 2008

• Handled in 2008 by a professional usability company

• 11 test subjects tested individually for 90 minutes. (5 students, 3 ph.d students and 3 scientists)

• Positive:

Clear indication of ressource types

Very useful option to limit results (facets)

Access to article search

Easy navigation and functionality

Search of unexpected resources was a positive surprise (discovery aspect)

• Negative:

Article search too hard to find (separate tab)

Too difficult to get full text access. (SFX)

Too many library terms on the interface

Advanced search not advanced enough

8


Recommendations of the usability test

• Resources: clear definition of content and coverage of resources

• Library terms: removed or translated to common language

• Contextual help: relevant help where needed

• Request and access: must be simplified and cleared of organizational issues

• Search options: focus on both ’Google users’ and advanced users

• Integrated search: aim for real integration – one interface, one search, one result set

• Social technologies: only use where relevant and of real value to the users

9


Impact of the CULIS consolidation project

• Ground breaking project and cooperation between UC and RLD

• Momentum was critical – compromise was the key

• Technical solution to organizational issues

• The Primo integration was an overall success … but

• Reflects complexity and flaws of the data layer

• Many policy and functionality discussions

• Know your customer! Know your strategy!

• ”The best is the good’s worst enemy”

10


Upgrading to Primo version 3 – first impressions

• Upgrade summer 2010

• Beta september – Live October 18

11


Upgrading to Primo version 3 – first impressions

• Seamless integration with Aleph logistics – almost

• Better integration with SFX link resolver

• Improved interface look and feel – farewell to pop ups

• More open platform – easier to integrate third party functionality

• Semi-intelligent feedback on user options in specific context

12


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

Requires close collaboration and cross consortia decissions

Requires a real active consortia organization

Requires a consortia ’owner’ and clear definition af responsibility

Requires constant focus on actions and consequenses

Not suitable for individual and equal institutions - with different proirities

13


Primo strategy for the near future

• Additional search options (MARC record view, push to external search engines)

• Third party integration (reference tools, mobile devices, social networks)

• Formalized design and terminology policies

• Complete new usability test with clear user profiles

• Focus on user satisfaction and fulfillment

• Be where the users are, on the users terms

14


The Royal Library long term Primo strategy

• Harmonize and standardize our data foundation

• Standardize and simplify our logistics and policies

• In principle achieve system independence

• Increasing focus on total cost of ownership

• Constant view on licensing, maintenance cost, automated work flows

• Primo as an exploratory search tool

• Primo as one stop search for all resources

• Full texts, images, maps, digital cultural heritage

15


Questions?

Royal Library Primo version 3:

http://rex.kb.dk

Ole Holm

Head of Library Service

The Royal Library, Copenhagen

[email protected]

16

Documents

PRIMO AT THE ROYAL LIBRARY OF DENMARK Integrated search – Google of the library? Helsinki, October 28 2010