As I mentioned earlier this week, I've been doing a lot of library instruction sessions recently. Over the past few years I've relied heavily on LibGuides for these one-shot sessions. The habit was to make a guide ahead of time, show students how to get to it during the class, and demonstrate library services and collections through the guide.
Then this past summer we adopted EBSCO's single discovery tool, EDS. I don't know if this is happening in other instruction sessions besides mine, but EDS is having an unintended consequence: Instead of immediately directing students to the LibGuide, I show them how to get to their LibGuide, tell them it's there for their subsequent reference, but then I go back to the main library web site and work from there. That big search box is too compelling to pass by, and it's too simple to ignore in favor of a LibGuide. Actually the entire library web page makes more sense when I can start with EDS, demonstrate how it works and what's there, and then segue into more specialized search tools and resources. We've been adding an EDS widget to the LibGuides, but somehow it seems a little silly.
Admittedly, this unintended consequence might be due to the nature of the classes I've been teaching. On Monday and Tuesday of the upcoming week, I'll be working with several Business classes that in the past have relied heavily on the LibGuides, and we'll see how they go. But one of the strengths of EDS is that you can throw almost any topic at it and guarantee results. Subsequently it's a great conversation starter and tool for demonstration.