Drupal & Summon: Keeping Article Discovery in the Library
13 likes4,008 views
The document discusses the integration of library resources through a Drupal-based platform using Summon, launched in September 2010, to enhance article discovery and user experience. It highlights the importance of keeping users engaged within their workflow by providing a seamless search interface, as well as the challenges faced with the integration of the Summon API and additional functionalities. Future plans include expanding services based on user needs and behavior, as well as improving the search and discovery capabilities offered by the library.
Drupal & Summon: Keeping Article Discovery in the Library
- 1. Drupal & SummonKeeping Article Discovery in the LibraryKen Varnum30 September 2011LITA National Forum
- 2. About the Library SiteLaunched 2 years agoRunning on Drupal 6 & SolrIntegrates discovery acrossCatalog (our books, ebooks including HathiTrust)Web content (stuff in Drupal)LibGuidesDatabases & Journals (metadata level)Articles
- 3. Where We WereHad Ex Libris’s Metalib federated searchUsed X-Server (XML interface) to pull results into siteDecent results butSlowInconsistentDid I say slow?
- 4. What We DidMLibrary signed up with Summon in July 2010Launched our interface 9/27/2010As with Summon’s hosted tool, anyone can search through our interfaceFull text links are OpenURLsUM authentication (off campus) / IP recognition (on campus) to get full text
- 5. About the ModuleDeveloped by Albert Bertram at UM LibraryRequires Summon API key to runDevelopment time about 10 weeksHad experimented with Summon API for another search projectBuilt code from scratch as a Drupal module
- 6. What It DoesReplicates most functionality of Summon’s hosted siteFacetsCitationsOne-click links to full text (where available)360 Link is resolverEach citation has a permalink for bookmarking/sharing
- 7. Module StatusAvailable as Drupal sandbox projecthttp://bit.ly/articlediscovery“Real” modules must be reviewed & approved by Drupal gatekeepersCan be slowIterative processMinimal benefit (for us)
- 8. Module ContributionUse GIT to download/updateOr download manually and install or upgradeAnyone can download & install RequirementsDrupal 6Php5phpapi client library rovidedby Serials SolutionsA couple pear packagesSummon API key
- 9. Search ResultsSummon NativeSummon @ MLibrary (API)
- 10. Item DisplaysSingle Item in SummonSingle Item in API
- 11. Why Do It This Way? Information world is a scary place (esp. for undergrads) Provide as few starting points as possible Keep users 'at home' as long as possible Provide access to help as much as possible Keep article discovery, catalog discovery, etc. in one context
- 12. Being in the FlowLorcan Dempsey defines “being in the flow” as:the library needs to be in the user environment and not expect the user to find their way to the library environmentintegration 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.“In the flow”, 6/24/2005http://orweblog.oclc.org/archives/000688.htmlImage courtesy of M.H Stephens
- 13. Staying in Our Own FlowWe *want* to be where the users areBut we need to start be being where we are.We’re not always sure where “there” isOur users’ flow often involves the library, so we also try to add extra value thereProvide auxiliary services within the local contextNot discourage users from going elsewhere, but providing reasons to stay
- 14. FlowingKeep discovery in the library.Send users to destination when they’ve found what they wantIn practice:LibGuide discovery in search & browseDatabase, journal, & catalog discovery in our siteIntegrate article discovery into siteSubject specialists integrated into search & browseProvide other services around article discoveryOpportunity to learn about our user’s needs and behaviors
- 15. DrawbacksFunctionality of Summon’s native interface does not wholly show in API (they have some very talented coders)Data doesNeed to do extra work on our side to, for example, display Web of Science Citation Counts, or LibGuide author photosAPI not 100% documentedWe’re now “help desk” for other libraries
- 16. EffectsEliminated Ex Libris’ Metalib & SFXChanges to external database usageDatabase discovery now in-siteAllows additional servicesFavoritesProblem reporting & response
- 19. How It’s Being Used
- 20. Failure ReportingFailure reportingAsk for feedback at point of full-text clickCapture permalink, on- or off-campus statusAsk for symptoms and email for follow-upQuestions pass through ask-a-librarian serviceRapid updates to our holdings inSummon/360 Link
- 22. Failure Report by Data Source423 reportsApril-September 2011
- 24. Where Next?Continue to build services around discoveryBring scoped searches to specific coursesLaunch sharing of frequently used & saved resources among students in a classContinue to study search & browse usage
- 25. Q&A Ken VarnumWeb Systems ManagerUniversity of Michigan [email protected]@varnumlib.umich.edu/users/varnum
Editor's Notes
- #2: BackgroundExperience with Summon & DrupalWhat we didWhyImpacts
- #8: Sandbox projects can be contributed to anyone; low-use modules optimal for this. Explicitly “experimental”. Lower barrier to sharing
- #12: Why do this when the Summon interface is, frankly, pretty good?
- #18: Metalib (in blue), ArticlesPlus (in red)
- #19: Metalib/ArticlesPlus (in blue), ArticlesPlus (in red)
- #20: Article searches look different from catalog & site searches