Drupal & Summon: Keeping Article Discovery in the Library


Published on

How building a Drupal module to bring Summon's article discovery system into our web site increased article searching, decreased direct database use, and maintained context for the library's patrons.

Published in: Technology, Education
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • BackgroundExperience with Summon & DrupalWhat we didWhyImpacts
  • Sandbox projects can be contributed to anyone; low-use modules optimal for this. Explicitly “experimental”. Lower barrier to sharing
  • Why do this when the Summon interface is, frankly, pretty good?
  • Metalib (in blue), ArticlesPlus (in red)
  • Metalib/ArticlesPlus (in blue), ArticlesPlus (in red)
  • Article searches look different from catalog & site searches
  • Drupal & Summon: Keeping Article Discovery in the Library

    1. 1. Drupal & SummonKeeping Article Discovery in the Library<br />Ken Varnum<br />30 September 2011<br />LITA National Forum<br />
    2. 2. About the Library Site<br />Launched 2 years ago<br />Running on Drupal 6 & Solr<br />Integrates discovery across<br />Catalog (our books, ebooks including HathiTrust)<br />Web content (stuff in Drupal)<br />LibGuides<br />Databases & Journals (metadata level)<br />Articles<br />
    3. 3. Where We Were<br />Had Ex Libris’s Metalib federated search<br />Used X-Server (XML interface) to pull results into site<br />Decent results but<br />Slow<br />Inconsistent<br />Did I say slow?<br />
    4. 4. What We Did<br />MLibrary signed up with Summon in July 2010<br />Launched our interface 9/27/2010<br />As with Summon’s hosted tool, anyone can search through our interface<br />Full text links are OpenURLs<br />UM authentication (off campus) / IP recognition (on campus) to get full text<br />
    5. 5. About the Module<br />Developed by Albert Bertram at UM Library<br />Requires Summon API key to run<br />Development time about 10 weeks<br />Had experimented with Summon API for another search project<br />Built code from scratch as a Drupal module<br />
    6. 6. What It Does<br />Replicates most functionality of Summon’s hosted site<br />Facets<br />Citations<br />One-click links to full text (where available)<br />360 Link is resolver<br />Each citation has a permalink for bookmarking/sharing<br />
    7. 7. Module Status<br />Available as Drupal sandbox projecthttp://bit.ly/articlediscovery<br />“Real” modules must be reviewed & approved by Drupal gatekeepers<br />Can be slow<br />Iterative process<br />Minimal benefit (for us)<br />
    8. 8. Module Contribution<br />Use GIT to download/update<br />Or download manually and install or upgrade<br />Anyone can download & install <br />Requirements<br />Drupal 6<br />Php5<br />phpapi client library rovidedby Serials Solutions<br />A couple pear packages<br />Summon API key<br />
    9. 9. Search Results<br />Summon Native<br />Summon @ MLibrary (API)<br />
    10. 10. Item Displays<br />Single Item in Summon<br />Single Item in API<br />
    11. 11. Why Do It This Way?<br /> Information world is a scary place (esp. for undergrads)<br /> Provide as few starting points as possible<br /> Keep users 'at home' as long as possible<br /> Provide access to help as much as possible<br /> Keep article discovery, catalog discovery, etc. in one context<br />
    12. 12. Being in the Flow<br />Lorcan Dempsey defines “being in the flow” as:<br />the library needs to be in the user environment and not expect the user to find their way to the library environment<br />integration of library resources should not be seen as an end in itself but as a means to better integration with the user environment, with workflow.<br />“In the flow”, 6/24/2005http://orweblog.oclc.org/archives/000688.html<br />Image courtesy of M.H Stephens<br />
    13. 13. Staying in Our Own Flow<br />We *want* to be where the users are<br />But we need to start be being where we are.<br />We’re not always sure where “there” is<br />Our users’ flow often involves the library, so we also try to add extra value there<br />Provide auxiliary services within the local context<br />Not discourage users from going elsewhere, but providing reasons to stay<br />
    14. 14. Flowing<br />Keep discovery in the library.<br />Send users to destination when they’ve found what they want<br />In practice:<br />LibGuide discovery in search & browse<br />Database, journal, & catalog discovery in our site<br />Integrate article discovery into site<br />Subject specialists integrated into search & browse<br />Provide other services around article discovery<br />Opportunity to learn about our user’s needs and behaviors<br />
    15. 15. Drawbacks<br />Functionality of Summon’s native interface does not wholly show in API (they have some very talented coders)<br />Data does<br />Need to do extra work on our side to, for example, display Web of Science Citation Counts, or LibGuide author photos<br />API not 100% documented<br />We’re now “help desk” for other libraries<br />
    16. 16. Effects<br />Eliminated Ex Libris’ Metalib & SFX<br />Changes to external database usage<br />Database discovery now in-site<br />Allows additional services<br />Favorites<br />Problem reporting & response<br />
    17. 17.
    18. 18.
    19. 19. How It’s Being Used<br />
    20. 20. Failure Reporting<br />Failure reporting<br />Ask for feedback at point of full-text click<br />Capture permalink, on- or off-campus status<br />Ask for symptoms and email for follow-up<br />Questions pass through ask-a-librarian service<br />Rapid updates to our holdings inSummon/360 Link<br />
    21. 21.
    22. 22. Failure Report by Data Source<br />423 reportsApril-September 2011<br />
    23. 23. Add-On Services<br />Favorites<br />Custom searches<br />Semi-permalinks<br />Failure reporting<br />
    24. 24. Where Next?<br />Continue to build services around discovery<br />Bring scoped searches to specific courses<br />Launch sharing of frequently used & saved resources among students in a class<br />Continue to study search & browse usage<br />
    25. 25. Q&A <br />Ken Varnum<br />Web Systems Manager<br />University of Michigan Library<br />varnum@umich.edu<br />@varnum<br />lib.umich.edu/users/varnum<br />