Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Summon @ LBSU

4,297 views

Published on

Presentation by Sue Carter, Ute Manecke and Mari Kermode, London South Bank University from the Summon and Information Literacy event at Queen Mary University, London.

Published in: Education
  • Follow the link, new dating source: ❤❤❤ http://bit.ly/369VOVb ❤❤❤
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Dating direct: ♥♥♥ http://bit.ly/369VOVb ♥♥♥
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Summon @ LBSU

  1. 1. Summon @ LSBU Sue Carter Ute Manecke Mari Kermode London South Bank University 10th November 2015
  2. 2. Introduction • Part 1: Choice and Implementation • Part 2: Testing and student training • Part 3: The Serials Perspective
  3. 3. Part I: Choice and Implementation
  4. 4. Background • LSBU needed to improve the user search experience for students and staff. • Federated search tools were passé – slow return of results and clunky user front-ends • LSBU had Encore which first came on the market in 2006 • BUT Encore alone was insufficient to meet the needs of LSBU’s students and staff – no article level index.
  5. 5. Encore at LSBU Encore’s single search box, search facets, and relevancy ranking option can be seen here.
  6. 6. LSBU’s requirements for a library discovery tool • A fresh approach was needed for a library discovery tool at LSBU. • LSBU’s requirements were: • First-class search engine with a single-search box • Article-level index based on a central index • One-stop shop for access to e-resources and the ability to harvest metadata from LSBU’s planned future repository. • Compatibility with LSBU’s library management system
  7. 7. Index-based Discovery Tools Index-based discovery tools had become popular in the HE sector at this time (2013). Two providers were invited to LSBU to give a demonstration: • Ebsco Discovery Service from Ebsco • Summon from Proquest
  8. 8. Decision Time • Both Ebsco and Proquest gave good demonstrations. • Testing – various teams within the Perry Library conducted standard searches to compare the two products. • Search terms such as King Lear and articles on hotel management in Turkey were looked for. • Both systems performed well in test searches. • Overall it was felt that Summon was more user-friendly and had a clearer front-end than Ebsco. • Summon was selected.
  9. 9. Implementation Overview • Labour-intensive but overall reasonably straightforward • Named technical support contact during the implementation phase • Proquest responded quickly to queries and problems • Number of implementation tasks which need to be carried out • Customisation and tailored search
  10. 10. Implementation Tasks …1 • ProQuest asked for basic information and configuration data such as: • How many records will you initially upload to Summon – it is initially necessary to send a full copy of your local catalogue metadata in MARC21 format to Summon • Which MARC field in your bib records contains the unique identifier • Information about the ftp upload process to get records into Summon
  11. 11. Implementation Tasks …2 • Next major task was filling out the content type mapping and MARC mapping spreadsheets • Fields from our library management system needed to be mapped to the Summon index and content types • Content type (Summon facets) have a default MARC field mapping
  12. 12. Implementation Tasks …3 • For both the content type and MARC field mapping, a library can choose to exclude a content type from mapping or to add additional mapping • Complex and time-consuming • You may need to do some tidying up of your catalogue records as a result of this process, be warned!
  13. 13. Implementation Tasks …4 Summon FTP Process • Need to send an initial upload of catalogue records to Proquest • Libraries need to set up an ongoing upload process • At the moment, fortnightly updates • A full copy of our catalogue records are sent quarterly to Proquest for Summon, to ensure consistency.
  14. 14. Summon Customisation • Best Bets – but over to Mari on this one • Database Recommender turned off • Two search boxes on student portal MyLSBU. A new Summon/tailored journal articles box alongside our usual library catalogue. • Summon tailored search widget was not at that time SSL (Secure Sockets Layer) compliant.
  15. 15. Summon Tailored Search …1 • Very concerned that we would not be able to use the Summon tailored search widget • Worked with Proquest and with our MyLSBU developers to use a vanilla version of Summon which could be used with MyLSBU • After thorough testing, working with LSBU ICT, we were able to use Summon with MyLSBU and go-live at the same time as the student portal launched. • However at that time the tailored search widget was still not SSL compliant – we had to have the full Summon with no tailored search.
  16. 16. Summon Tailored Search …2 • We decided to call our Summon search box “Find Journal Articles and More” anyway, as Summon is the best way to find articles even without a tailored search. • This story has a happy ending. • The Summon tailored search widget is now SSL compliant. • So in the near future we can finally have our tailored article search in the library MyLSBU pages.
  17. 17. Summon search in MyLSBU Summon is behind the right hand search box here
  18. 18. Part II: Testing and student training
  19. 19. Summon testing • Testing in the ALD team in the summer of 2014 • Worked through exercises and focused on: • searching different types of resources, i.e. books, journals, journal articles, DVDs etc. • by title or by keywords • filtering searches • exporting some results
  20. 20. Summon testing • We also thought about • its name • default search settings • order of filtering options
  21. 21. Summon testing Feedback after testing: • Many issues! • Catalogue? Summon? Databases? • Most of these issues were resolved
  22. 22. Student training • First few weeks before it went on the student portal: • Some of us showed new students the Summon link and demonstrated a search • From November 2014 – August 2015: partly demonstrated on the student portal • From September 2015 for the new academic year: Summon was strategically introduced in inductions and sometimes in other training sessions.
  23. 23. Student training • Target audience • Mainly first-year undergraduates and foundation students • When to use it • As an initial keyword search for journal articles to see how much there is on a particular subject or topic • If used, it should normally be followed on by a specific database search. • For citation searching, i.e. to find a particular item.
  24. 24. Student training • Content usually demonstrated • Main search box • Results display • Main filtering options on the left hand side • Content sometimes demonstrated • advanced search settings • Content occasionally demonstrated • Creating an account and saving search results
  25. 25. Advantage of Summon Benefit for users: • Ease of use: quick and simple way of finding articles
  26. 26. The Library catalogue Choosing a database Looking through the archive Finding the issue THE ARTICLE! Finding a specific journal article The old way:
  27. 27. Find journal articles or more Summon THE ARTICLE! Finding a journal article The new Summon way:
  28. 28. Disadvantages of Summon • Summon not equally useful for searches in different disciplines • Filtering to full text • “Find journal articles and more”!
  29. 29. Part III: The Serials Perspective
  30. 30. My Role • Collate feedback (still ongoing!) to create ‘big picture’ of LSBU user experience with Summon • Identify whether concerns need support from the Systems team or from the Serials team • (The above point isn’t always obvious to our users!) • Create Best Bet entries for databases
  31. 31. • High uptake of Summon! • Several e-journal access queries coming via Summon discovery route • Queries coming from both LSBU students & staff • Information provided by ProQuest helped to clarify queries from library staff “in-house” The Good
  32. 32. • Skewed search results in Summon vs results specific databases for identical searches • Trying to make certain features do something they’re not designed to do The Not so Good
  33. 33. Best Bet Results • Forced to select one database for each subject area, not great for discovery!
  34. 34. • Testing problems to differentiate between a Summon problem and an e-resource problem • Created “ticket” spreadsheet to assist with this…. Currently
  35. 35. • Move to a truly tailored article search • Make greater use of statistics to inform Summon settings • Happy with Summon, but continue to keep abreast of other discovery tools to ensure that Summon is the best fit for LSBU Summon Future …
  36. 36. Any questions? Email: Sue.carter@lsbu.ac.uk maneckeu@lsbu.ac.uk kermodem@lsbu.ac.uk

×