Archives for posts with tag: Summon

It’s been a long while since we’ve updated this blog, and we have made significant progress in implementing Summon. We even have a name for the service, CityLibrary Search, which trips off the tongue nicely! There is a big milestone looming for us at the moment, the go-live date, which is (currently) the end of August, when we will make Summon the primary search tool via the Library’s home page. More on this when it happens.

In the meantime, I thought I would write about one of the thorniest problems we have been trying to deal with. This is the issue of “known database searching” using Summon. The idea here is that it is sometimes (often?) the case that users are uninterested in performing a full pre-indexed federated search, and instead just wish to get to a specific database. For example law students are likely to want quick access to one or both of the two big legal information databases, Westlaw and Lexis Library. This is borne out by user behaviour: we see a large number of searches for known databases in our current library catalogue, Encore.

Therefore it is important that any discovery service (or indeed library catalogue) can provide quick access to any given named database. Encore does a pretty good job at doing this- see for example this search for Westlaw, where said database comes up top of the list of hits, with a prominent link through to the database itself. Summon is, I would argue, less good on this score. A search for Westlaw comes up with lots of hits. At the top of the list is a “Recommendation”, which is a link through to Westlaw, but in my view the link is not particularly prominent, and it is also not very clear that the link will take you to that database. The rest of the regular Summon hits are, essentially, noise- a variety of articles that happen to mention Westlaw in some context or another, but which certainly won’t provide an authenticated link through to the database itself. Summon does have a “Database Recommender” function, but this seems to be erratic in its operation, for example throwing up irrelevant recommendations.

So, what is to be done? Our current thinking is that we will upload our Millennium LMS Electronic Records Management (ERM) records (a tautology I know!) to Summon, and class these as databases which are “our own” content, which will hopefully push the database records up the hits list. You can see an example of the ERM record for Westlaw in Summon here– the problem is that currently you have to specify the facet “Database” to be able to retrieve the relevant hit, something that few if any users are likely to do. Using ERM records will also allow us to specify alternative names for databases- to use the Westlaw example again, Westlaw does much better when searched for in Summon using its “real” name, Westlaw UK (see hit number two).

Another possible approach (perhaps to be done in tandem with the ERM records approach above) will be that taken by the Queensland University of Technology’s Summon implementation. They have uploaded their Libguides A-Z list as structured XML into Summon’s index as local holdings. This appears to do a good job of creating database links, though they seem to be categorised as “Web resources”, not as databases proper. You can view a presentation on this approach here (requires a Google Drive log-in).

So, the short version: it’s complicated, but pretty vital to get right. We don’t want to try to direct users to Libguides whenever they need access to a database because (as user behaviour stats show) they legitimately expect to be able to access databases via Summon itself. I’ll follow this post up if and when we have found a satisfactory solution.

Lucy’s previous post gave the background as to why we and other academic library people think resource discovery tools are potentially useful tools for library users. This post reflects on the decision-making process that led us to choose Summon over other available products.

The first thing to say about the process is that it was hard, particularly in negotiating the politics that often come into play when proposing any relatively major change in systems! There was a feeling amongst library managerial staff that a resource discovery tool would in principle be useful and cost-effective, but that feeling was by no means a general one. Some members of library staff (and particularly subject specialists) had quite legitimate concerns about the coverage of discovery tools in general, and of Summon in particular. Discovery tools do well for coverage of STEM subjects, but (arguably) less well with Arts, Humanities and Social Sciences, and there are a few subjects (notably law, a significant area of study here at City) which have gaps in coverage. I won’t write more about these issues at the moment,but they are ones we will return to in future posts.

Once we had decided that we wanted a resource discovery tool, the next question was, which one? We decided to limit the scope of the procurement decision-making process to the current generation of discovery tools (new tools are on the horizon already) which for practical purposes meant choosing between SummonPrimo and EBSCO Discovery Service (EDS).

We started off by visiting a number of institutions (LSE, Middlesex, Brunel) who have recently implemented discovery tools, not so much to see the tools in action (though that was of course interesting) but to get an idea of how they decided between the tools they considered and to find out how they managed the procurement and implementation processes. These visits were invaluable, not least to reassure ourselves that a lot of the issues we were considering were not unique to us. Running parallel to this, we invited each supplier in to present on their product, also inviting a number of colleagues to these demonstrations. This gave us an idea of the functionality and relative strengths and weaknesses of the products.

After the demonstrations, we invited colleagues to vote on their preferred option. We offered the following options:

  • I prefer Primo
  • I prefer Summon
  • I prefer EDS
  • I think we should get a discovery tool, but I have no clear preference
  • I don’t think we should get a discovery tool

We also invited feedback on the various products and on the reasons for or against getting a discovery tool. The results of this exercise saw a clear majority in favour of getting a discovery tool, but no overwhelming majority in favour of any particular product (though for the record Summon did get most votes).

The final stage of the process was to do a detailed analysis of the functionality of each product, as well as other important factors such as cost and fit with current systems. The result of this analysis (as you might be able to guess) was that Summon was the preferred choice. We felt that Summon and Primo offered pretty similar functionality, but that Summon was clearly a better fit with our current systems (we use Serials Solutions’ knowledge base 360 Core) as well as being priced lower than Primo. We felt that EDS did certain things well (not least exposing EBSCO’s own large dataset of publications), but that it didn’t offer true pre-indexed federated search. We then took a paper to the Library Executive team, who passed the paper.

So now all we have to do is implement Summon!