Friday, 16 July 2010

Naming our Primo installation

One of the preliminary discussions that we had early on in our project was what to call our Primo installation. It soon became clear that there were two distinct options. We could either try to retain some continuity or we could choose a completely new name to indicate that this is a brand new system.

As we are planning to use Primo to completely replace our Library Catalogue and eLibrary (MetaLib) interfaces we could try to retain some continuity by using a slightly amended form of these names. To this end Library Catalogue Plus and eLibrary Plus were suggested. Certainly we have seen examples of other Primo sites where the word Plus has been added to the current Library Catalogue name, so this felt like a valid possibility.

The alternative option was to think of a brand new name and after much discussion we decided on two possibilities. These were SearchLight and LOCATe. We thought SearchLight could indicate that you were shining a light onto your search in order to find information. The name LOCATe could stand for Library Online Catalogue, and of course the word locate also means find. It was agreed that if either of these names were selected we would also need a strap line which would summarise what the system does.

As we were having these discussions just before the end of term we decided to try to get some student input into which name our users preferred. In order to try to reach as many people as possible we used two methods to get feedback. Firstly, we went around the Library and asked users if they could spare a few minutes to give us their views. To those that were happy to do this we explained briefly about the plan to introduce Primo and asked them which name they liked best. Secondly, we created a SurveyMonkey poll where we again explained about Primo and asked which of the four names respondents preferred.

We received just under 150 responses, split very evenly between online and face-to-face. Unfortunately, the results weren’t completely conclusive, although there were two names that came out ahead. These were eLibrary Plus and LOCATe and both had a similar number of votes. As term was ending and there wasn’t time to do another student poll it was decided to survey the Library staff and ask them to choose between these two options. This time there was a more conclusive result and the name LOCATe was chosen.

A very useful side benefit of carrying out the user survey about the name was that we also asked for volunteers to take part in our usability testing over the summer. We knew this was likely to take place in July or August, so we asked everyone who gave us input about the name if they lived close enough to the University to come in over summer and if so whether they were interested in taking part in some testing if there was a financial incentive. As a result of this we got 40 volunteers, all of whom gave us their email addresses and said we could contact them when we were arranging the testing. This was a big relief as one of our concerns had been how we would contact users about the tests during the quiet summer period.

Tuesday, 15 June 2010

Budget

JISC require that an outline budget is posted, so here is the budget for the covprimo project:


Projected Timeline, Workplan & Methodology

The following chart details the main work packages as identified by Ex Libris in their Primo Implementation project plan and the timescales they are working to. Local tasks such as the usability testing and the launch and publicity have then been planned to take place at appropriate times.

Tuesday, 25 May 2010

Project Team Relationships and End User Engagement

The project team at Coventry consists of the following members:
Caroline Rock – University Librarian (JISC Project Champion)
James Fisher – E-Resources Co-ordinator (JISC Project Manager)
Graham Daniels – Head of Electronic and Network Services (Primo Implementation Project Manager)
Sandy Forster – Head of Bibliographic Support (providing input on the management of bibliographic records from the Aleph Library Management System)
Paul Smith – Library Systems Manager (carrying out most of the technical developments on the Library side)
Theresa Morley – Assistant Subject Librarian (giving a user-focussed view to the project) Carolyn Haresign – Head of Academic Services (also giving a user-focussed view and providing experience of running focus groups)
Joanne Marsh - Repository Development Officer (providing input on integrating the University’s repository (Equella) with Primo)

The majority of the Coventry project team can be seen in these photos.

The project team from Ex Libris consists of the following members:
Georg Heiming, Ex Libris, Germany (Project Manager)
Lee Smith, Ex Libris, UK (working on Coventry Primo implementation for Ex Libris)
Leonard Wright, Ex Libris, UK (working with Lee on Coventry Primo implementation for Ex Libris)

Engagement with end users has already started with a survey to consider potential names for the CU Primo product when it is launched. Once the initial version of Primo has been made available usability testing will be carried out and the results of this testing will be used to inform changes that will be made to make the interface more intuitive. During the survey about the name for Primo, respondents were asked if they would like to volunteer to take part in usability testing over the summer and 40 people volunteered, leaving their details so they can be contacted about taking part in the testing.

Tuesday, 18 May 2010

Intellectual Property Rights

As required by JISC the case study report and all other outputs will be published using the Creative Commons Attribution-Share Alike UK 2.0: England and Wales license.

Managing risks and success

The intention is to launch Primo in time for the start of the new academic year in September 2010, although it will continue to be developed and tested after the launch. If for some reason this is not achieved the contingency plan is to carry out a soft launch at a slightly later date, making Primo available alongside the current Library Catalogue and MetaLib systems. These other interfaces will then be removed later on, leaving Primo as the single user interface, for searching for Library material.

The risks that have been identified relating to the project are listed below, along with the actions required to mitigate against those risks.
1. The risk of losing key personnel can be reduced by building expertise across the team.
2. The risk of delays due to inter-departmental dependencies can be reduced by ensuring effective internal communication and the inclusion of relevant staff in the team.
3. The risk of delays due to supplier dependencies can be reduced by agreeing the implementation timescale in the contract.
4. The risk of the unavailability of stakeholders for consultation and feedback can be reduced by effective project planning and the offering of incentives and by engaging with stakeholders early in the project.

Since starting the project the team has realised that there is a risk to authenticating via Shibboleth with the Aleph Library Management System, which the technical members of the team are working to resolve.

It is hoped that Primo will be very popular with the users at Coventry. There are no major problems anticipated as a result of this. However, we do need to be aware of the resource implications of continuing to develop the product and ensure that there is staff time set aside to do this.
Similarly, if the case study report is well received this shouldn’t cause any problems.

Tuesday, 11 May 2010

Benefits from the project to Coventry University and the wider community

The introduction of Primo should benefit the users at Coventry by providing a simpler search experience and making information retrieval easier as previously outlined. It will also simplify searching by providing a single point of access when linking from other student systems, such as the VLE and student portal. This should help to improve student satisfaction. The new interface should also increase confidence that the best use is being made of the Library’s resources.

The case study and usability testing should benefit the wider community by deepening the understanding of the information seeking behaviour of the ‘google generation’, piloting Web 2.0 technologies, testing the adequacy of harvestable metadata and testing the interoperability of related information systems. It should also be of benefit to the Primo community who may want to use the report to inform changes to their own Primo interfaces.
 
Creative Commons License
This work is licenced under a Creative Commons Licence.