Posts Tagged ‘Library ICT systems’

Find it @ Lincoln: looking forward to a new EBSCO discovery service in the Library

Posted on May 11th, 2012 by Paul Stainthorp

Following long, looong discussions, we have finally chosen a next-generation library discovery service for the University of Lincoln Library.

After reviewing the four major commercially-available discovery products (from EBSCO, Ex Libris, OCLC and Serials Solutions), and after making several reference visits to see the various products in action in UK university libraries…

(…drum roll…)

EDS logo…we decided upon, and have now bought access to, the EBSCO Discovery Service. Over the summer we’ll be configuring and testing the new system, and in September 2012 it’ll be launched as the new front-end search and discovery platform for the Library at the University of Lincoln.

This new service will provide a single point of search and discovery across nearly all of the Library’s collections, including our ‘traditional’ library catalogue, e-books & e-journals, the Lincoln Repository, archives & special collections, reading lists, and a wide range of specialist and general electronic databases. (N.B. it might not search all of these collections right from day one!) We hope that—along with some of the other new and improved services that are being introduced as part of the Library’s review of ICT systems—it will make it significantly easier and more straightforward to find and use the University’s library resources.

According to the SCONUL HE Library Technology wiki, the EBSCO Discovery Service is also used by:

We decided that EBSCO Discovery Service provided us with a familiar (yet flexible, powerful and ‘serious’) research interface, as well as a good fit with our existing and planned electronic database collections. We were also influenced by EBSCO’s plans to develop and integrate the A-to-Z e-journals knowledgebase and link resolver into the discovery environment.

We’ll be spending the next month or so configuring the system to search all of our collections, designing/branding the interface, training library staff, and working with other University departments on getting the most out of the new tools. We anticipate that early access to the system will be possible from the end of July onwards (though this is subject to change), with a ‘soft’ launch in time for student induction in September, and a formal launch/discovery party with free coffee for all, later in the year.

We have also decided that the service will be branded under the title “Find it @ Lincoln“. (Eagle-eyed readers will spot that this is the name we’ve been using for a while for our EBSCO LinkSource OpenURL link resolver.) Information about the new Find it @ Lincoln service, and about the project to develop and launch it at the University of Lincoln, will soon be available at: http://findit.library.lincoln.ac.uk/

I’d like to thank the staff of all four discovery software companies, for all the presentations, demonstrations & visits, for the information they made available to the University of Lincoln over the past few months about their products, and for the demonstrations and supporting materials they provided which were of such use in informing this first selection phase of our discovery project.

Many thanks also, to the several universities who received staff from Library for discovery-themed visits, and who patiently described their use of their own search tools and answered our many questions profound and otherwise.

Now watch this space :-)

Imminent domain

Posted on May 4th, 2012 by Paul Stainthorp

With various new services arising out of the ongoing Library ICT systems review, we’re amassing a nice little collection of library-related 2nd-level subdomains. Here’s a list, which I’ll edit as they become live.

  1. http://library.lincoln.ac.uk/ (i.e. the ‘bare’ library subdomain: this isn’t used at the moment, but we intend that it will become the Library’s ‘root’ web presence)
  2. http://www.library.lincoln.ac.uk/ (currently used for our SirsiDynix Horizon Information Portal OPAC, which we intend to move to catalogue.library… in order to free up www for our web pages hosted on WordPress)
  3. http://catalogue.library.lincoln.ac.uk/ (the future home of the library catalogue)
  4. http://catalog.library.lincoln.ac.uk/ (an alternative/US spelling of catalogue)
  5. http://findit.library.lincoln.ac.uk/ (a launch point for our new Discovery system, still to be announced, and with a name yet to be decided!)
  6. http://lists.library.lincoln.ac.uk/ (Talis Aspire reading lists, currently being developed)
  7. http://archives.library.lincoln.ac.uk/ (Axiell Calm archives and special collections software)
  8. http://jerome.library.lincoln.ac.uk/ (Jerome is our innovation platform and a home for experimental search services, being re-developed as part of the CLOCK project)
  9. http://auth.library.lincoln.ac.uk/ (OpenAthens LA v2.1 authentication software)
  10. http://proxy.library.lincoln.ac.uk/ (EZProxy authentication software)
  11. http://guides.library.lincoln.ac.uk/ (LibGuides software)

We also have two core systems which aren’t on the library subdomain:

  1. http://eprints.lincoln.ac.uk/ (the Lincoln Repository on EPrints – it’s appropriate that this isn’t on library, as we’ve always managed the Repository as a shared/collaborative project between CERD, ICT services, the Library, and the Research Office)
  2. http://ill.lincoln.ac.uk/ (CLIO inter-library loans software)

How commercial next-generation library discovery tools have *nearly* got it right

Posted on May 17th, 2011 by Paul Stainthorp

In Huddersfield (again – I’m barely away from the place!), yesterday, at a CILIP UC&R (University, College and Research Group) Yorkshire & Humberside [catchy name] training event on ‘Discovering Discovery Tools‘. Librarians from four different UK universities gave practical, pros-and-cons descriptions of how they implemented and are now running four different commercial next-gen resource-discovery tools:

Five (count ‘em!) people from Lincoln were in the audience. I was wearing two hats: one for project Jerome for thinking about design concepts in resource discovery tools; the other for my day job – Lincoln is in the middle of a strategic review of Library ICT systems, which may well end up recommending that we buy one of these products.

It was all good stuff. First off, libraries need to hear the honest, warts and all counterpoint to the glowing terms in which each discovery product is described by its vendor. Secondly, it’s useful to subject all four* resource discovery platforms to the same amount of daylight, and see where the common problems lie, as well as where one tool outperforms another. Thirdly—and even though there’s a lot of resource discovery hyperbole to be heard—this is still a big shift for academic libraries, and I think we should discuss implications that are wider than the costs/benefits for an individual institution.

(*Yes, I know there are a few other tools. But they weren’t in the room yesterday.)

Lockside
What’s stopping us? (Canal lock gate at the University of Huddersfield.)

Things that jumped out at me:

Commercial resource discovery has reached a level of maturity that was absent a couple of years ago. That’s not to say that all next-gen resource discovery tools are perfect (because they aren’t), or that there aren’t any problems (because there are; see below), but academic libraries do now have a genuine choice between several different, viable commercial products.

Here’s a heresy: the differences between these four products are not that significant. I think that anyone who went away from yesterday’s event thinking that out of the four discovery tools on display there are some ‘good’ and some ‘bad’ …is probably wrong. It’s not really about the product, it’s about the willingness of the vendor to overcome problems, and about their attitude to their customers. Do you buy a slightly-less slick product, but from a company you feel you can have a more productive relationship with?

In fact, most of the real problems with resource discovery seem to be common to all four of the products on show yesterday. De-duping via FRBR reckons to be a bit of an Achilles’ heel. (A shame. FRBRisation is one of those things you either need to get right, or not do at all. A half-arsed attempt is worse than not bothering.)

Also broken: known-item search. This ought to be trivial to fix, and it needs to be sorted now now now.  I find it particularly sinister that some commercial resource-discovery tools rank their search results according to secret, proprietary algorithms that can’t be inspected or challenged by their users, let alone altered/improved. This is a problem. What’s the point of a library that can’t justify how its resource discovery system actually works? Are we just here to sign the cheques?

Libraries still have a tendency to overcomplicate things for their users. Sometimes they do this because they have no choice (perhaps their shiny new discovery tool doesn’t quite work they way it should); but often they seem just too ready to accept a situation where users are inconvenienced sooner than address an underlying problem. Lincoln included in this sweeping generalisation.

There’s no point pretending that a library can make two independent decisions to purchase [a] a next-gen resource discovery platform, and [b] a journals knowledgebase/link resolver. The two things are all tied up together. To pick a random example: you want Summon, you’d better want 360.

Why can’t we just buy access to a search index? If I want to pay to provide my users with the benefits of a lovely big central index of content, why do I have to buy into your discovery algorithm and web front-end as well? (Whither JISC collections?)

Related, and finally – we really shouldn’t have to replace our search and discovery interfaces every time we want/need to use a different content provider, and we shouldn’t be placed in the situation of having to make collection/subscription decisions in order to ‘feed’ our discovery tool. It may be temptingly easy, cost aside, to pick up and put down different next-gen discovery products (“…it’s just a subscription!”) but there’s too much at stake for our users.