Discovery Here, Discovery TherePros and Cons of Local & Remote Hosting of Discovery Tools                                 ...
Introduction• 5+ years at University of Michigan Library• 12+ years in academic, corporate, and special  libraries• Fondne...
Agenda•   What is discovery?•   Local vs. remote hosting of interface•   What it takes to host an interface locally•   Pro...
Discovery DefinedFor today’s talk, discovery systems have thesequalities:• A central index of metadata & full text• Harves...
Discovery SystemsThings you’ve heard of:• EBSCO Discovery System• Ex Libris Primo• Serials Solutions Summon• WorldCatSee a...
Vendor Model
Massey University (New Zealand)Conversation Starter at ALA AnaheimJune 23, 2012
Massey University (EBSCO)Conversation Starter at ALA AnaheimJune 23, 2012
Boston UniversityConversation Starter at ALA AnaheimJune 23, 2012
Boston University (Primo Discovery)Conversation Starter at ALA AnaheimJune 23, 2012
Dartmouth CollegeConversation Starter at ALA AnaheimJune 23, 2012
Dartmouth College (Summon)Conversation Starter at ALA AnaheimJune 23, 2012
What Do Users Experience?• An interface that generally does not look like  their home library• A clean, elegant, & tested ...
What Do Libraries Gain?•   Simplicity of setup and interface design•   Discovery is just another vendor•   Autopilot (more...
API Model
University of ToulouseConversation Starter at ALA AnaheimJune 23, 2012
University of Toulouse DiscoveryConversation Starter at ALA AnaheimJune 23, 2012
Universitätsbibliothek FreiburgConversation Starter at ALA AnaheimJune 23, 2012
Universitätsbibliothek FreiburgConversation Starter at ALA AnaheimJune 23, 2012
NCSU LibrariesConversation Starter at ALA AnaheimJune 23, 2012
VillanovaConversation Starter at ALA AnaheimJune 23, 2012
What Do Users Experience?• A familiar interface• Integration with other library services• ComfortConversation Starter at A...
What Do Libraries Gain?•   Control over user experience•   Knowledge of what your users are doing•   User-specific usage t...
University of MichiganConversation Starter at ALA AnaheimJune 23, 2012
Michigan Discovery via APIConversation Starter at ALA AnaheimJune 23, 2012
What We Enable• Full-text link failure help• Favorites• Data AnalysisConversation Starter at ALA AnaheimJune 23, 2012
Problem Reporting• Article full-text links clicked: 134,095• There were 310,171 article searches• Problem reporting is bui...
Results of Error Reporting• Reports go to our online reference service, Ask  a Librarian• Each one reviewed & responded to...
Problem Reports by Data Source      doaj_primary_oai, 1.2%  webofscience_primary_A                   53 other           , ...
Favorites• Can save articles for future use• Soon will be able to organize with other library  resourcesConversation Start...
Favorites version 2.0Conversation Starter at ALA AnaheimJune 23, 2012
What You Need•   A vendor with an API•   Programming staff to customize it•   Commitment to keeping up with changes•   Wil...
Why Do This?• Users have familiar navigation• Library can offer appropriate assistance• We are guardians of patron interac...
DiscussionKen Varnum                               Drupal in LibrariesWeb Systems Manager                      ALA TechSou...
Upcoming SlideShare
Loading in...5
×

Discovery Here, Discovery There: The Pros and Cons of Local & Remote Hosting of Discovery Tools

1,541

Published on

Discovery systems are powerful tools to help users find information resources across the breadth of the library's online holdings. Many of these tools offer APIs for libraries to build their own user interfaces to the search index, allowing a library to keep site visitors within the library until the time they access the full text of a resource. What are the pros and cons of keeping discovery local? This talk explores the user interaction, interface design, and user expectations of such homegrown interfaces.

Download from the University of Michigan: http://hdl.handle.net/2027.42/91892

Published in: Technology, Education
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,541
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • Abstract:Discovery systems are powerful tools to help users find information resources across the breadth of the library's online holdings. Many of these tools offer APIs for libraries to build their own user interfaces to the search index, allowing a library to keep site visitors within the library until the time they access the full text of a resource. What are the pros and cons of keeping discovery local? This talk will explore the user interaction, interface design, and user expectations of such homegrown interfaces.
  • What are we talking about, anyway?All the links I’m talking about are available through
  • You can see why I’m not a graphic designer.
  • Not picing on this or any other library – they’re just examples of what I’m illustrating.
  • T
  • – you manage the contract & track uptime & Commonality of interface: not really an advantage, I think – most people don’t flit from discovery interface to discovery interface. You get a new one when you change schools, move, or the library’s vendor changes
  • Université to Toulouse (France)
  • Freiburg University Library (Germany) - -EBSCO Discovery Service API
  • Freiburg University Library (Germany) - -EBSCO Discovery Service API
  • Integrate Many Sources
  • Maintain User-Friendly Distinctions
  • It’s where the search interface lives. The index always lives elsewhere, at the vendors’s site. A couple pictures will illustrate
  • Université to Toulouse (France)
  • Data since March 1-April 30, 2012Data independent of vendorAll of these are proxies for utility to user.Matched with query & user informationFavoritingProblem links. Do they use it? Boy, do they ever. 1070 times in winter semester from 310,000 searches (these numbers are different from Google’s – it’s what was searched,
  • Proxy: the resource isn’t proxied at all, or a new “hop” was put in place between the original URL and the targetUser account: all sorts of odd things. Expired users, alumni who don’t know they can’t have access; registrar problems, you name itResource: the database doesn’t work, it’s no longer licensed, catalog is wrong
  • Winter 2012
  • Citations have “persistent” links – short term, not long. Good for a day or three, but not a semester. We depend on Summon to not overwrite the identifier – they make no promises about persistence). We can save all the bibliographic data needed to build a reliable OpenURL. So when someone returns to a favorite, we have all the necessary data to find it again for them.Beginning to analyze data from 9,000 favorite items / 1,000 patrons
  • Launching an integrated tool with foldersHave longer-term goal of dynamically connecting resources & classesStarting to tie resources to specific classes (for an academic setting)For public libraries, this could be tied to HS or community college courses, or common research tasks that you know your population follows.We think this will help us get a sense of what people are actually using, so we can compare to what faculty are requiring (readings lists). Will help us with instruction, tailored support materials.
  • By “as long as possible”, I mean as long as needed for a particular interaction. Beginner needs more opportunities for correction, guidance, backtracking. Competent searcher may need assistance rarely, but still can use guidance and familiar tools. Advanced searcher may not be using the discovery tool, but possibly should be in the “right” database in the first place.Once we send our patrons off on the “information superhighway”, who knows what might befall them?
  • Discovery Here, Discovery There: The Pros and Cons of Local & Remote Hosting of Discovery Tools

    1. 1. Discovery Here, Discovery TherePros and Cons of Local & Remote Hosting of Discovery Tools Ken Varnum University of Michigan Library varnum@umich.edu @varnum Conversation Starter at ALA Anaheim June 23, 2012
    2. 2. Introduction• 5+ years at University of Michigan Library• 12+ years in academic, corporate, and special libraries• Fondness for two library things: – Drupal (not talking about that here today) – DiscoveryConversation Starter at ALA AnaheimJune 23, 2012
    3. 3. Agenda• What is discovery?• Local vs. remote hosting of interface• What it takes to host an interface locally• Pros and Cons• QuestionsConversation Starter at ALA AnaheimJune 23, 2012
    4. 4. Discovery DefinedFor today’s talk, discovery systems have thesequalities:• A central index of metadata & full text• Harvested from many sources• Integrated with full text delivery• Something you license• NOT federated/brokered/broadcast search• Understands library’s holdings/rightsConversation Starter at ALA AnaheimJune 23, 2012
    5. 5. Discovery SystemsThings you’ve heard of:• EBSCO Discovery System• Ex Libris Primo• Serials Solutions Summon• WorldCatSee a list of who uses what at bit.ly/LIDDXcConversation Starter at ALA AnaheimJune 23, 2012
    6. 6. Vendor Model
    7. 7. Massey University (New Zealand)Conversation Starter at ALA AnaheimJune 23, 2012
    8. 8. Massey University (EBSCO)Conversation Starter at ALA AnaheimJune 23, 2012
    9. 9. Boston UniversityConversation Starter at ALA AnaheimJune 23, 2012
    10. 10. Boston University (Primo Discovery)Conversation Starter at ALA AnaheimJune 23, 2012
    11. 11. Dartmouth CollegeConversation Starter at ALA AnaheimJune 23, 2012
    12. 12. Dartmouth College (Summon)Conversation Starter at ALA AnaheimJune 23, 2012
    13. 13. What Do Users Experience?• An interface that generally does not look like their home library• A clean, elegant, & tested interface• Some challenges in “resetting” themselves or getting help• Unclear who “owns” the interactionConversation Starter at ALA AnaheimJune 23, 2012
    14. 14. What Do Libraries Gain?• Simplicity of setup and interface design• Discovery is just another vendor• Autopilot (more or less)• Anyone who has used a discovery interface can use your vendor’sConversation Starter at ALA AnaheimJune 23, 2012
    15. 15. API Model
    16. 16. University of ToulouseConversation Starter at ALA AnaheimJune 23, 2012
    17. 17. University of Toulouse DiscoveryConversation Starter at ALA AnaheimJune 23, 2012
    18. 18. Universitätsbibliothek FreiburgConversation Starter at ALA AnaheimJune 23, 2012
    19. 19. Universitätsbibliothek FreiburgConversation Starter at ALA AnaheimJune 23, 2012
    20. 20. NCSU LibrariesConversation Starter at ALA AnaheimJune 23, 2012
    21. 21. VillanovaConversation Starter at ALA AnaheimJune 23, 2012
    22. 22. What Do Users Experience?• A familiar interface• Integration with other library services• ComfortConversation Starter at ALA AnaheimJune 23, 2012
    23. 23. What Do Libraries Gain?• Control over user experience• Knowledge of what your users are doing• User-specific usage tracking information• Ability to intercede• Ability to offer help & additional servicesConversation Starter at ALA AnaheimJune 23, 2012
    24. 24. University of MichiganConversation Starter at ALA AnaheimJune 23, 2012
    25. 25. Michigan Discovery via APIConversation Starter at ALA AnaheimJune 23, 2012
    26. 26. What We Enable• Full-text link failure help• Favorites• Data AnalysisConversation Starter at ALA AnaheimJune 23, 2012
    27. 27. Problem Reporting• Article full-text links clicked: 134,095• There were 310,171 article searches• Problem reporting is built in to our interfaceConversation Starter at ALA AnaheimJune 23, 2012
    28. 28. Results of Error Reporting• Reports go to our online reference service, Ask a Librarian• Each one reviewed & responded to (phew!)• Frequent classes of problems: – User account problems – Proxy problems – Resource problemsConversation Starter at ALA AnaheimJune 23, 2012
    29. 29. Problem Reports by Data Source doaj_primary_oai, 1.2% webofscience_primary_A 53 other , 1.4% sources, 10.8% credo_entries, 1.6% gale_primary, 3.2%crossref_primary, 4.4% LOGICAL, 41.6% pubmed_primary, 5.1% webofscience_primary, 1 1.2% proquest_dll, 19.4% Conversation Starter at ALA Anaheim June 23, 2012
    30. 30. Favorites• Can save articles for future use• Soon will be able to organize with other library resourcesConversation Starter at ALA AnaheimJune 23, 2012
    31. 31. Favorites version 2.0Conversation Starter at ALA AnaheimJune 23, 2012
    32. 32. What You Need• A vendor with an API• Programming staff to customize it• Commitment to keeping up with changes• Willingness to experiment (a bit) and shareConversation Starter at ALA AnaheimJune 23, 2012
    33. 33. Why Do This?• Users have familiar navigation• Library can offer appropriate assistance• We are guardians of patron interactions; should keep that connection alive as long as possible.Conversation Starter at ALA AnaheimJune 23, 2012
    34. 34. DiscussionKen Varnum Drupal in LibrariesWeb Systems Manager ALA TechSourceU. of Michigan Library 978-1-55570-778-1varnum@umich.edu@varnumLink List:bitly.com/bundles/varnum/3 http://amzn.to/drupalinlibrariesBackground image by MLibrary – CC: BYConversation Starter at ALA AnaheimJune 23, 2012

    ×