from google scholar to “library search” via koha: a different journey to discovery services?...

From Google Scholar to “Library Search” via Koha:A different journey to discovery Services?David Peacock, Information Collections & Services ManagerUniversity of Hertfordshire

https://library.herts.ac.uk/

Outline of presentation:

• Background to the University of Hertfordshire (UH)

• Library Search Project: What we wanted to achieve.

• Why an open source LMS? Why work with a third party developer?

• Why a Discovery service? Why not just use Google Scholar?Why did we completely replace our Library OPAC with a discovery service?

• Outcomes – Have we achieved what we wanted to achieve?

• Initial feedback / usage statistics?

University of Hertfordshire (UH)

• 2 LRCs, open 24/7, provide the University with; 3,000 study places; 1,200 computer workstations; over 40,000 current online and print journal; and over 875,000 books (incl. 375,000 online ebooks).

• Voyager LMS since 1999• Relied on Google Scholar as our Discovery

platform and Voyager OPAC – integrated within our in-house VLE

The old search interface:

The New search interface:

The New search interface:

What we wanted to achieve (1)

• Improve student experience/satisfaction by providing easier, consistent search discovery of library resources in a single “google” like search box.

• Continue to embed library discovery search within the Universities Online learning Environment.

• Replace the outdated Voyager Library Management System (LMS) with a modern integrated low cost, hosted, open source software solution for remaining LMS functions.

What we wanted to achieve (2)

• Increase use of UH library collections /resources increasing Value for Money (VFM) in existing substantial investment

• Provision of additional search functionality and access / delivery of resources

• Provision of search functionality tailored to particular groups of students via module pages.

• Significantly lower annual revenue cost than the current Voyager annual support agreement

• Increased workflow efficiencies in back end library processes, with the potential to add a further resource management platform onto of the LMS at a later stage, at minimal additional cost.

• Improve management information, business intelligence for better decision making / VFM.

Why an open source LMS?

• Lower costs• Avoiding vendor lock-in• Open Standards –

– Increased adaption, customisation and innovation – fast development environment (UH rather unique service -Unmediated ILLs)

– Easier integration and interoperability with other University and Library Systems. Pace – “today interoperability in library automation is more myth than reality”

• Opportunity for more Agile developments – adopt a more “start-up” culture.

• Excellent third party support – no need for a high level of IT support.

• Being part of a wider worldwide community

LMS Integration needed

LMS

Student finance / WPM Online

Payments

VLE Online Library

VLE Learning Analytics

Discovery Layer/ Reading lists

IDM / SSO / ADFS

Student / Staff System

Role of the Supplier in OSS terms:

• Commitments on; Functionality; Cost; Timescale; Service Levels

• Hosting (SaaS)• Installation and configuration of LMS• Data conversion and loading into LM• Training & on-going support• Software development• Custom / integration work• Bug fixes and upgrades

Why a Discovery Service? Why not continue to use Google Scholar? (1)

Issues with Google Scholar:• No University control over Google.

– “Google thought they were being searched by a robot and showed our users a captcha”

• Lack of transparency and control over indexing coverage.

• Inability to highlight and/or increase relevancy of UH resources.

• Google Scholar cannot be tailored to local circumstances

• Print books and many –ebooks resources remain excluded.

• Problems interfacing and linking to UH resources.

Why a Discovery Service? Why not continue to use Google Scholar? (2)

Benefits of a Resource Discovery System:• Potential access to everything found. • Single search box for all resources including print.• High quality transparent metadata/indexing. • Full text searching of UH ebooks. • Increased use of subscription resources• Increased level of refinement and improved

functionality• Easy integration with VLE / module resources• Greater choice of outputs.

Why a Discovery Service? Why not continue to use Google Scholar? (3)

• Potential replacement of the Library OPAC. • Easier Management of Demand Driven

Acquisition (DDA) Resources. • Improving information literacy training• Greater Personalisation.

But we still encourage use of Google Scholar

Aaron Tay : “5 things Google Scholar does better than your library discovery service” • Google Scholar updates much quicker• Covers scholarly material not on usual "Scholarly"

sources   • Greater and more reliable coverage of Open Access

and free sources• Better Relevancy due to technology and the need

to just support article searching• Nice consistent features

–Have we achieved what we wanted to achieve?

• Improved Student experience / satisfaction (?) Single “google” like search box Embedded within the VLE Replace Voyager with an Open source VLE• Increase usage /VfM (?) Provide additional functionality Search functionality tailored to module pages Significantly lower annual revenue costs Increased workflow efficiencies in back-end library

processes• Improved Management Statistics (?)

Outcomes: Have we achieved what we set out to achieve?

Initial usage statistics…..Comparison of Aug – Nov 2014 and 2015

• 33 Journal and database publishers – saw an overall increase so far of 18% on the same period (August – November) in the previous year. (JR1 Counter reports or equivalents).

Highlights include:– Emerald – up 60%– Project Muse – up 205%– EbscoHost titles – up 59%– Taylor and Francis – up 60%– ProQuest – up 255%

• E-book usage (BR1 Counter reports or equivalents):– EBL – up 28%– Safari – up 3%– Dawson's – 21%

• Inter Library Loans (Aug-Dec):- 37% Decrease in the number of ILLS requests submitted (saving £4,300)

• UH Research Archive:– 267% increase in hits

Initial usage statistics…..Comparison of Oct– Nov 2014 and 2015 (1)

• 51573 referrals to 360 link from Google Scholar (Oct-Nov 2014)

• 289734 referrals to 360 link from Summon (Oct-Nov 2015)

• 462% increase in 360 referrals

In conclusion:

• Resource Discovery Services give substantial benefits over Google Scholar. But Google Scholar still has its uses!

• RDS seem to increase usage of UH subscribed resources

• OSS is a viable, cost effective, mainstream option, especially when you work with an experienced commercial third party support company

• Use the opportunities of the open Standards within OSS for fast development and integration at minimal risk

Bibliography

• Chad, K., (2016) “Rethinking the library Services Platform”http://helibtech.com/file/view/Rethinking_the_LSP_Jan2016.pdf/571294475/Rethinking_the_LSP_Jan2016.pdf

• Kemman, M (2013) “What if Google killed Scholar”http://www.maxkemman.nl/2013/09/what-if-google-killed-scholar/

• Kortekass, S., (2012) “Thinking the unthinkable -doing away with the library catalogue”

http://insights.uksg.org/articles/10.1629/2048-7754.174/

• Spezi, V et al (2013) “Impact of Library Discover technologies: a report by UKSG”

http://www.uksg.org/sites/uksg.org/files/UKSG_final_report_16_12_13_by_LISU.pdf

• Tay, A. (2015) “Musings about Librarianship: 5 things Google Scholar does better than your library discover service”

http://musingsaboutlibrarianship.blogspot.co.uk/2015/07/5-things-google-scholar-does-better.html#.VpPbzvmLSUk

Thank you!

David Peacock d.m.peacock@herts.ac.uk

Information Collections and Services Team Library and Computing ServicesUniversity of Hertfordshire