A discovery case study

946 views

Published on

EBSCO Discovery Service at Cowles Library, Drake University,
Teri Koch
Marc Davis,
ILA/ACRL
3/18/2011

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

  • Be the first to like this

No Downloads
Views
Total views
946
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

A discovery case study

  1. 1. A Discovery Case Study<br />EBSCO Discovery Service at Cowles Library, Drake University<br />Teri Koch<br />Marc Davis<br />
  2. 2. What is “web-scale discovery?”<br />A service <br />capable of searching quickly and seamlessly across a vast range of local and remote content [and of]<br />providing relevancy-ranked resultsusing the type of intuitive interface that today’s information seekers expect. <br />Adapted from:<br />http://americanlibrariesmagazine.org/news/ala/explore-web-scale-discovery-services-new-issue-library-technology-reports 2/1/2011<br />
  3. 3. Discovery<br />OCLC WorldCat Local<br />Serials Solutions Summon<br />EBSCO Discovery Services<br />Ex Libris Primo Central<br />Blacklight is an OSS OPAC/faceted “discovery” tool based on Ruby<br />(see http://projectblacklight.org)<br />Stanford’s Searchworks: http://searchworks.stanford.edu/<br />University of Virginia’s Virgo: http://search.lib.virginia.edu/<br />
  4. 4. Discovery 3-Year Project Plan<br />Year One (Implementation)<br />Initial deployment/UI<br />Deploy specialized instances<br />Year Two (Assess)<br />Assessment<br />Usability<br />Year Three (Review)<br />Service (DISCOVERY) <br />Vendor<br />
  5. 5.
  6. 6. Why implement?(1) Effective use of resources – “access goal”<br />
  7. 7. Why Implement?(2 & 3)<br />The googlizationof research behaviors<br />User expectations impact research behavior <br />Speed, simplicity, massive result sets<br />An “attractive” library search<br />Speed, simplicity, massive result sets<br />Can search become research through result quality?<br />Dissatisfaction with federated search<br />Pedagogy<br />Can we spend more time teaching research skills and less time teaching tools/interfaces?<br />Impact on IL?<br />
  8. 8. EDS at Drake: SuperSearch<br />SuperSearch<br /> over 100 databases, library catalog, IR (D-Space).<br />Specialized Instances<br />13 databases, library catalog<br />SUPERSEARCH MOBILE BETA<br />
  9. 9. Specialized Instances<br />Included in Biology SuperSearchAccess Science EncyclopediaACS Publications--Journal Search AMA: JAMA & Archives JournalsAnnual Reviews Biological AbstractsCredo ReferenceDrake University CatalogGale Virtual Reference LibraryGale: GREENR (Global Reference on the Environment, Energy, and Natural Resources)GreenFILEInternational Pharmaceutical AbstractsJAMA, the Journal of the American Medical AssociationJSTORMEDLINENatural Standard Nature Science Magazine ScienceDirectScopus<br />
  10. 10. Rationale for Implementation 1<br />Access (Integrating knowledge base resources)<br /> . . . searching quickly and seamlessly across a vast range of local and remote content . . . <br />Achieved. <br />Improvements to catalog records (quality)<br />Continued additions to content sources <br />Addition of ContentDM repositories, summer 2011<br />Resource level impacts are not yet determined: cf statistics<br />
  11. 11. Rationale for Implementation 2<br />Googlization<br />Aligning the user’s search expectations & experiences<br />Mixed. <br />It’s really not very Google-like (not just a box)<br />User expectations (elasticity in the box)<br />Complexity of full-text retrieval (nothing new)<br />Limitations of federated (integrated) search<br />
  12. 12. Rationale for Implementation 3<br />Pedagogy – tailor instruction to where the user is at in research process<br /> -- Reduce # of interfaces*<br /> -- Many students only receive one library session in their college careers : SuperSearch . . . specialized SuperSearch<br />Mixed, trending to achieved.<br />Jury still out on specialized instances<br />Disrupted existing pedagogies & expectations for some<br />Customizations (Go to Database) (internal)<br />Student expectations (it’s still not Google) (or Wikipedia)<br />Doing too much for students, too many results/confusing (external)<br />FYS* fewer interfaces taught, IL stronger (authority) <br />
  13. 13.
  14. 14. EDS Process<br />LOC - Executive<br />SUPERSEARCH IMPLEMENTATION TEAM<br />Teri Koch –Team Leader.<br />Sean Stone --Pharmacy/Science Librarian. Learning & Pedagogy/Training<br />Andrew Welch – ILS Project Librarian. ILS Integration/ Interface/Training<br />Susan Breakenridge–Marketing Coordinator.<br />Marc Davis –Technical Coordinator.<br />Kay Kelly – Electronic Resources Manager. <br />Chris Purcell – Web Developer. <br />Rod Henshaw– Library Dean.<br />Year One Activity:<br />Deployment/Development<br />Adds Bruce Gilbert, Dir. Instruction/Campus IL<br />Year Two Activity:<br />Assessment.<br />RESOURCES<br />Partnership with EBSCO.<br />Direct contacts.<br />Discussion List.<br />Webinars. <br />Experimentation.<br />
  15. 15. Wiki for EDS Implementation<br />http://supersearch-implementation.drake.wikispaces.net/<br />
  16. 16.
  17. 17. Training and Promotion of EDS<br />Marketing (usual +)<br />Putting the “super” in SuperSearch.<br />Search you can trust.<br />Training <br />Librarians & staff<br />Faculty (liaison & more)<br />Students (all entering freshman)<br />Basic SuperSearch video<br />
  18. 18. Press Releases<br />EBSCO: http://www.prweb.com/releases/DrakeUniversity/ChoosesEDS/prweb4386674.htm<br />Drake Web Site: http://www.drake.edu/news/db/official/archive.php?article=6113<br />
  19. 19.
  20. 20.
  21. 21. Impacts: Year 2 Questions<br />Quantitative (searches, full text retrievals, sessions, etc.); impacts on individual resources<br />Quantitative measures are insufficient but vital<br />Statistics before and after EDS are confusing<br />Impacts on IL, Learning Outcomes?<br />Anecdotal – Feedback from instructors, generally positive, though some think it is too advanced for freshmen<br />Assessment criteria/ – Have new GenED Librarian starting in June; this will be one of his/her primary assignments<br />Usability<br />
  22. 22. Searches: 2009/10LGBT Life with Full Text: Ebsco<br />
  23. 23. Full Text: 2009/10LGBT Life with Full Text: Ebsco<br />
  24. 24. Searches: 2009/10Business Source Complete<br />
  25. 25. Full Text: 2009/10Business Source Complete<br />
  26. 26. Lies, Damn Lies and . . . <br />Workarounds for statistics on mailing list<br />COUNTER guidelines need to be updated<br />Vendors may not be prepared for Discovery’s impact<br />Surge in number of searches<br />Simultaneous user licensing not congenial<br />
  27. 27. Multiple Profiles<br />Search Origins<br />
  28. 28. Discovery 3-Year Project Plan<br />Year One (Implementation)<br />Initial deployment/UI<br />Deploy specialized instances<br />Year Two (Assess)<br />Assessment<br />Usability<br />Year Three (Review)<br />Service (DISCOVERY) <br />Vendor<br />

×