350 likes | 650 Views
DWT is focused on providing state-of-the-art federated search products and solutions which search, retrieve, aggregate and analyze content from web-based databases. ...
E N D
Slide 1:Not All Federated Search Engines are Created Equal
Abe Lederman, President and CTO Deep Web Technologies, Inc. Next Generation Library Technologies, May 7, 2008
Slide 2:Who We Are…
Founded in 2002 Headquartered in Santa Fe, New Mexico 20 Employees Over $2 million in R&D funding DWT is focused on providing state-of-the-art federated search products and solutions which search, retrieve, aggregate and analyze content from web-based databases.
Slide 3:Abe Lederman-Background
Earned B.S. and M.S. Computer Science degrees, MIT Began work in information retrieval in 1988 Co-founded Verity Developed some of the first web-based applications that searched text-based content, 1994 Pioneered “Deep Web” searching in 1999 Founded Deep Web Technologies, 2002
Slide 4:Some of Deep Web’s Customers
Department of Defense DOE Office of Scientific and Technical Information Intel Corporate Library National Agricultural Library Scitopia.org Stanford University
Slide 5:What is Federated Search?
Federated Search is an application or service that allows a user to submit a search in parallel to multiple, distributed information sources and retrieve aggregated, ranked and de-duped results.
Slide 6:In Other Words…One Search, Many Sources
Library Catalogs Blogs & Wikis Subscription Sources Public Web Sources E-Books News
Slide 7:Benefits of Federated Search
One-stop access to multiple information sources Users don’t need to know where/how to search Saves researcher time and money Improves utilization of information sources Consolidated, ranked and de-duped results Important results are not missed
Employees often asked, “Why can’t the Intel Library site work like Google or Yahoo?” Federated Search at the Intel LibraryGeothermal Heating
Slide 13:Why Aren’t all Federated Search Engines Equal?
Quality of search results User Interface Results Delivery Administrative Console
Slide 14:Quality of Search Results
Thorough connector development Boolean and Fielded Searching Number of results retrieved from each source Relevance Ranking of retrieved data
Slide 15:User Interface
“Intuitive” navigation Rich feature set Display of results incrementally Integration with library’s website (supports multiple search pages) Powerful web 2.0 interface
Slide 16:Results Delivery
Aggregated, ranked results Clustering/grouping of results Analysis tools such as filters and sorts Results Export to RSS, Email, Citation manager Alerts
Slide 17:Administrative Console
Enable/disable connectors Create search boxes and search pages easily Metrics
Source: Agricola Query: Corn Ethanol Sort By: Date
Time to Deliver: 1 second
Time to Deliver: 6 seconds
Time to Deliver: 2 seconds Federated search engines have varying strengths and weaknesses. Select the federated search that is best for your organization. Bottom Line
Slide 23:Recommendations
for selecting the “best” federated search engine for your library.
“Basically, anything that results in a more enjoyable search experience, will lead users to spend more time with a particular federated search product and thus derive value from those highly relevant results, assuming they are easy to find. This is where a pleasant and uncluttered layout, intuitive navigation, and a good amount of Ajax to minimize page refreshes combine with highly relevant search results to create the perfect user experience. From The Federated Search Blog www.federatedsearchblog.com Sponsored bySlide 25:What Is Important(and what’s not)
Information Discovery Analysis Features Time-Saving Full-Text Access Quality of Results Intuitive Interface Elegant Presentation Ranking Internal Sources Premium Content Sources User Satisfaction Simplify Access Standards Clusters – Facets – Visualizations Metadata Alerts Real-Time Search Cost Administrative Interface
Slide 26:Bringing Federated Search to your Library
Clearly Define Your Organization’s Requirements Create Evaluation Criteria Evaluate Vendors Test-Test-Test
Slide 27:Narrowing Down Your Vendor Choices
Slide 28:Clearly Define Your Organization’s Requirements
Compile your list of sources to federate Determine sources to search from each search page Licensed Product vs. Managed Solution Budget Staff Resources Timelines Determine features important to users
Slide 29:Compile a list of requirements and features a vendor must provide. Add additional features you would like to have. Create a vendor checklist. Evaluate responses.
Create Evaluation Criteria
Slide 30:Sample Vendor Checklist:Company Viability
Slide 31:Sample Vendor Checklist:Architecture and Integration
Slide 32:Sample Vendor Checklist:Connectors
Slide 33:Sample Vendor Checklist:Results Display
Slide 34:Vendor Evaluation
Demonstrations and Pilots Is a pilot necessary? How long of a pilot? Should we do multiple pilots? Conduct focus groups Fulfillment of requirements and features Remember: Federated Search is a long-term commitment to a vendor.
Slide 35:Test-Test-Test
Scripting your tests Test each engine against the same criteria (same queries, same sources) Break-dancing How sturdy is the engine? Vendor Response How quickly (or slowly) does the vendor respond to your needs?
Slide 36:The Future of Federated Search
Multi-lingual searching Personal libraries Automated source selection Integration with social networking tools
Slide 37:Deep Web’s Search Gallery
Slide 38:Resources
The Federated Search Blog www.federatedsearchblog.com Sample Vendor Checklist Email me: abe@deepwebtech.com Federated Search: Solution or Setback for Online Library Services Edited by Christopher Cox
Thank You! Abe Lederman abe@deepwebtech.com