Discovery Hosting Options
•
5 gostaram•2,007 visualizações
This document discusses the pros and cons of locally hosting discovery tools versus using remotely hosted vendor solutions. It notes that locally hosting through an API model allows libraries to customize the user experience and interface, gain usage analytics, and provide direct user support. However, it requires programming resources to implement and maintain. Using a vendor model is simpler to set up but libraries have less control over the user interface and experience and interaction. The document explores examples of libraries using both models and the advantages each can provide.
Recomendados
Recomendados
Mais conteúdo relacionado
Semelhante a Discovery Hosting Options
Semelhante a Discovery Hosting Options (20)
Mais de Ken Varnum
Mais de Ken Varnum (18)
Último
Último (20)
Discovery Hosting Options
- 1. Discovery Here, Discovery There Pros 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. 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) – Discovery Conversation Starter at ALA Anaheim June 23, 2012
- 3. Agenda • What is discovery? • Local vs. remote hosting of interface • What it takes to host an interface locally • Pros and Cons • Questions Conversation Starter at ALA Anaheim June 23, 2012
- 4. Discovery Defined For today’s talk, discovery systems have these qualities: • 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/rights Conversation Starter at ALA Anaheim June 23, 2012
- 5. Discovery Systems Things you’ve heard of: • EBSCO Discovery System • Ex Libris Primo • Serials Solutions Summon • WorldCat See a list of who uses what at bit.ly/LIDDXc Conversation Starter at ALA Anaheim June 23, 2012
- 6. Vendor Model
- 7. Massey University (New Zealand) Conversation Starter at ALA Anaheim June 23, 2012
- 8. Massey University (EBSCO) Conversation Starter at ALA Anaheim June 23, 2012
- 9. Boston University Conversation Starter at ALA Anaheim June 23, 2012
- 10. Boston University (Primo Discovery) Conversation Starter at ALA Anaheim June 23, 2012
- 11. Dartmouth College Conversation Starter at ALA Anaheim June 23, 2012
- 12. Dartmouth College (Summon) Conversation Starter at ALA Anaheim June 23, 2012
- 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 interaction Conversation Starter at ALA Anaheim June 23, 2012
- 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’s Conversation Starter at ALA Anaheim June 23, 2012
- 15. API Model
- 16. University of Toulouse Conversation Starter at ALA Anaheim June 23, 2012
- 17. University of Toulouse Discovery Conversation Starter at ALA Anaheim June 23, 2012
- 18. Universitätsbibliothek Freiburg Conversation Starter at ALA Anaheim June 23, 2012
- 19. Universitätsbibliothek Freiburg Conversation Starter at ALA Anaheim June 23, 2012
- 20. NCSU Libraries Conversation Starter at ALA Anaheim June 23, 2012
- 21. Villanova Conversation Starter at ALA Anaheim June 23, 2012
- 22. What Do Users Experience? • A familiar interface • Integration with other library services • Comfort Conversation Starter at ALA Anaheim June 23, 2012
- 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 services Conversation Starter at ALA Anaheim June 23, 2012
- 24. University of Michigan Conversation Starter at ALA Anaheim June 23, 2012
- 25. Michigan Discovery via API Conversation Starter at ALA Anaheim June 23, 2012
- 26. What We Enable • Full-text link failure help • Favorites • Data Analysis Conversation Starter at ALA Anaheim June 23, 2012
- 27. Problem Reporting • Article full-text links clicked: 134,095 • There were 310,171 article searches • Problem reporting is built in to our interface Conversation Starter at ALA Anaheim June 23, 2012
- 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 problems Conversation Starter at ALA Anaheim June 23, 2012
- 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. Favorites • Can save articles for future use • Soon will be able to organize with other library resources Conversation Starter at ALA Anaheim June 23, 2012
- 31. Favorites version 2.0 Conversation Starter at ALA Anaheim June 23, 2012
- 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 share Conversation Starter at ALA Anaheim June 23, 2012
- 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 Anaheim June 23, 2012
- 34. Discussion Ken Varnum Drupal in Libraries Web Systems Manager ALA TechSource U. of Michigan Library 978-1-55570-778-1 varnum@umich.edu @varnum Link List: bitly.com/bundles/ varnum/3 http://amzn.to/drupalinlibraries Background image by MLibrary – CC: BY Conversation Starter at ALA Anaheim June 23, 2012
Notas do Editor
- 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?