-
Recent Posts
- Tech Sharecase, 8 December 2017
- Technology Sharecase, 10 November 2017
- Tech Sharecase, 20 October 2017
- Tech Sharecase, 8 September 2017
- Tech Sharecase, 5 May 2017
- Tech Sharecase, 21 April 2017
- Tech Sharecase, 18 November 2016
- Tech Sharecase, 23 September 2016
- Tech Sharecase: 28 July 2016
- Tech Sharecase on 10 May 2016
-
Archives
- December 2017
- November 2017
- October 2017
- September 2017
- May 2017
- April 2017
- November 2016
- October 2016
- July 2016
- May 2016
- October 2015
- September 2015
- May 2015
- April 2015
- November 2014
- June 2014
- April 2014
- March 2014
- February 2014
- January 2014
- October 2013
- September 2013
- August 2013
- July 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- October 2012
- September 2012
- July 2012
- June 2012
- May 2012
- March 2012
- February 2012
- January 2012
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
-
Meta
Tag Archives: Google Custom Search
A Search Box to End All Search Boxes
I’m intrigued by libraries that are trying to find creative ways to cut down on the number of places users have to go to search for information. First, we had federated search tools that sent out searches to a bunch of places and aggregated the results; now we’re seeing discovery layers (like Summon, Primo, EBSCO Discovery, WorldCat Local, VuFind, Project Blacklight, etc.) that aggregate content into a single index and offer search results more quickly than federated search typically can. Still, these new discovery layers may not be the ideal search tool for every silo the library owns or licenses.
Our students, trained by Google to look for a single search box to rule them all, are probably looking for unified search tools on our site. While discovery layers are great and all the rage now, it seems like some libraries have accepted that discovery layers may not be the ideal solution for searching all the silos or presenting results from those silos. If you take a look at what the libraries at North Carolina State University have done, you’ll see that the “Search All” box on the library home page presents results from different silos and spreads those results out on the search results page into different clusters. Check out what happens if you do a search there for “market share.” Notice the way that the articles are presented via the discovery tool (Summon), the books via the catalog, and other categories of content via other search tools:
This federated “search all” feature on the NCSU libraries web site actually pulls together a number of different search tools, which are explained more fully elsewhere on the site.
Librarians at the Leddy Library at the University of Windsor are at work now on a tool called Jamun that does something similar: it gives the user a single search box that will do a federated search across several different silos and present those results spread across the page in different categories. This project is being built using a Google Custom Search engine. You can learn more about it from the video recording the presentation about it at the recent Code4Lib North event and by checking out Mita Williams’ blog post about it (which includes an embedded slidecast) and Art Rhyno’s blog post from April.
[kml_flashembed movie="http://www.youtube.com/v/aZGqCFSZGAg" width="425" height="350" wmode="transparent" /]
Posted in Uncategorized
Tagged Discovery tools, Federated search, Google Custom Search, Summon
Comments Off on A Search Box to End All Search Boxes