I’ve been looking seriously at metasearch/federated search products for libraries recently. After a lot of reading and a few demos I’ve got some complaints.
I’m surprised how vendors, even now, devote so much time demonstrating patron features that are neither used nor appreciated by any patrons without an MLS. Recent lessons (one, two, three) should have made it clear that libraries need to conform to patron expectations of how online resources should work. Our own search statistics show that only 0.0067% (YES, less than a hundredth of a percent!) of the searches on our OPAC get “limited” to specific languages, locations, dates, or material types. What our patrons expect is that a natural language search will yield relevant results in the first page of hits. “Googlization” isn’t about dumbing things down, it’s about making the technology smarter.
And that’s the problem with these vendor’s metasearch products. They don’t do much to improve the quality of the results retrieved from any database. Shovelware, products that pile up junk in an attempt to generate value based on quantity, is poor solution for libraries or researchers. Still, that’s how these products work, and it’s how they’ll continue to work until libraries and their database providers adopt some of the advances in search technology now used on the web (it’s not just Google, but Yahoo, Teoma, Clusty, and others).
At the same time these metasearch products are doing little to improve the results we get, they’re also making the search process slower. Why do they all make us wait while slowly updating a table that shows only the number of hits retrieved from each database? A9 can teach all these vendors quite a few lessons on that point. A9 reports results in resizable columns, and fills in the details from various databases as they become available. The biggest lesson A9 can teach these vendors, however, is that metasearch should be free. They’re pushing OpenSearch as a public standard based on RSS/XML and already they’ve got access to 236 databases. That’s not bad compared to z39.50 (which we all still respect as the elder parent of current search standards), but remember that the standard was only announced in March 2005.
We need to pressure database vendors to improve their search engines and give better results. Maybe database providers need to rank journal articles by the number of citations they receive? Maybe libraries need to buy Google Search Appliances and do their own indexing of database content. That way, links from university faculty would increase the rank of articles they link to, making search results especially relevant.
Then, we need to ask where our money is going when we buy software like this. We need to demand standards-based products with outstanding ease of use. Go try out A9 and compare it to anything in your library. Yeah, don’t you wish you could offer that to your patrons?
tags: a9, clusty, federated search, google, libraries, library, library systems, metasearch, natural language search, opac, patron, patrons, search technology, teoma, yahoo
Posted July 10, 2005 by Casey Bisson
Categories: Libraries & Networked Information, Technology. Tags: a9, clusty, federated search, google, libraries, library, library systems, metasearch, natural language search, opac, patron, patrons, search technology, teoma, yahoo.
8 Comments
Comments RSS
TrackBack Identifier URI
Leave a comment
User contributed tags for this post:
pink world com (1833) - WWW PINK WORLD COM (275) - pinkworld (265) - pinkworld com (208) - pink pussy com (191) - pink world (162) - http pink world com (151) - www.pink world.com (83) - sexfilm (81) - pink com (59) - pussy com (58) - pink pussy (54) - www.pink pussy.com (47) - PINK WORLD S (40) - com pinkworld (34) - free pussy com (30) - www.pink warld.com (29) - WWW.pink would.com (26) - WWW COM PINK WORLD (25) - www.pinkworld.com (24) - http://www.PINK WORLD.com/ (23) - world pink com (21) - com pink world (21) - WWW PINK COM (20) - pink world.com (20) - indian pussy com (19) - WWW WORLD PINK COM (19) - metasearch products (19) - WWW PINK WORLD SEX COM (18) - search pinkworld (18) - animal pussy com (17) - metalib cost (16) - PINK PUSSY WITH ANIMAL (16) - federated search (16) - pinkworld www com (15) - pinkworld.www.com (15) - WWW COM PINKWORLD (15) - www.pink.com (14) - animal sexfilm (14) - WWW PINK WORLD (13) - metalib api (13) - libraries (13) - www.pink wrold.com (13) - pink wrold (12) - pinkworld animal (12) - http pink world (12) - WWW.COM PINKWORD (12) - pink tv (12) - WWWPINK WORLD COM (12) - IN (11) - free sexfilm (11) - WWW PINK PUSSY COM (11) - PINK WWW COM (10) - free pink world com (10) - sexygirl com (10) - wwwpink world.com (10) - www.com.pinkworld (9) - PINK WORLD WWW COM (9) - www.world sex.com (9) - pink wrold.com (9) - http://www.pink world.com (9) - pink warld.com (9) - clusty api (9) - Search http pinkworld com (9) - pink world free (9) - pink world sex (9) - sex300 (8) - www pink would com (8) - pink wopld (8) - show the pussy com (8) - all (8) - pinkworld.animal (8) - high cost of metasearch for libraries (8) - pink animalpussy (8) - www.pink world sex.com (8) - metalib pricing (7) - free animal sexfilm (7) - pink would.com (7) - http pink pussy com (7) - metalib x server (7) - WWW PINKWORLD COM (7) - www.world pussy.com (7) - pussy world com (7) - world pussy com (7) - free pink world (6) - i need pussy com (6) - pink pussy.com (6) - pinkworld sex (6) - pink world ltd (6) - pink world sex.com (6) - pinkworld animals com (6) - dumbing things down making the technology smarter (6) - crack sexfilm (6) - www.com.pink world (6) - clusty (6) - XServer metalib (6) - www.pink world .com (6) - pink would com (5) - mss (5) - www.world.sex.com (5) - http://pink world.com (5) - WWW. PINK WORLD.COM (5) - www com pink (5) - WWWPINK WORLD (5) - wwwpink TV (5) - metasearch product (5) - www.sex world.com (5) - http://pink world com (5) - world animal sex com (5) - world pink (5) - google earth free com (5) - pinkworld pussy (5) - federated search cost (5) - metalib costs (5) - com pinkword (5) - www.world pink.com (5) - metasearch libraries (5) - metalib crack (5) - metalib xserver (5) - metasearch vendor (4) - animal pinkworld (4) - www.pink world . com (4) - www.pink.world.com (4) - google eart free version (4) - www sex warld.com (4) - Show The Pussy C O M (4) - pink.www.com (4) - PINK WROLD COM (4) - Wwwpink world sex.com (4) - www.pink sex.com (4) - www.sex.wrold.com. (4) - sexygirl rank in the world (4) - www pink wrold com (4) - com pink world com (4) - www pink warld sex (4) - http:PinkwORLD.COM (4) - metasearch api (4) - a9Deferred (4) - http WWW PINK WORLD COM (4) - pussy.com (4) - federated search price library (4) - pinkworld;com (4) - wwwpink tv com (4) - http/pinkworld.com (4) - Search pink world (4) - www.world sex .com (4) - federated search build your own connector (4) - WWW Pink tv com (4) - a9 (4) - get pussy com (4) -
[...] MetaLib (with SFX) is where the bells and whistles are really obvious. There are varying degrees of increased complexity in the interface depending on how deep you go. This is great for the librarians, but unlikely that students would use it. In fact Casey at MaisonBisson, also in attendance with me, states that “only 0.0067% (YES, less than a hundredth of a percent!) of the searches on our OPAC get “limited†to specific languages, locations, dates, or material types” in his article The High Cost Of Metasearch For Libraries. The interface seems to be minimally customizable, limited to headers, footers, and CSSS. However, there are “real” APIs for MetaLib, a separate product they call XServer. It is well documented and seems to be just the right amount of useful, but more cumbersome than a mere REST-like interface. [...]
What do you think of this article?
http://www.adtmag.com/article.asp?id=11385
Unfortunately, vendors don’t sell to patrons, but to librarians. They have to add the full Boolean bells and whistles to get past the all-librarian screening committee. Most are senior staff, raised on Dialog.
[...] A9, the search engine from Amazon.com, does some pretty interesting things that libraries should be aware of. First, any library considering a metasearch product should look at what can be done for free, and second, libraries should take a look at the OpenSearch technology that drives it. [...]
[...] What about RSS, XML, OpenSearch? WordPress solves the RSS feed for us (look at this URL to see). A feature-complete XML API, is a bit further off, but maybe somebody wants to pitch in to help solve that one? And full OpenSearch support, taking advantage of the suggested and alternate search features, is my next big project (here’s where I’m going with that). [...]
Our library system is using a mix of tools: MetaFind from Innovative Interfaces as the “connector”, but running our own front-end (in PHP) that queries other databases thru MetaFind. Our relevance rank tweaked Metafind’s “relevance ranking” (which was, “10 results from whatever database answered first, 10 results from the second, etc) to ignoring the response time of each database (but preserving each database´s original “relevance” rank. However, it turns out that most users didn´t like the relevance algorithm for each individual database… it didn’t seem google-like enough. Brittanica ignores phrase matching as “higher relevance”, ProQuest seems to put articles higher based solely on term occurence… so taking whatever (limited) results came back from each metasearch, we now implemented an algorightm with high scent (pushing results up based on term occurence, phrase occurence, and newer publication date) which seems to be working better (I guess we need more studies to find the right scoring weights). I know the vendors won’t get to this soon enough, so why not tweak our metasearch engines like this in the meantime? BTW, if you want to look at this algorithm tweak, look at our results (sorry, it’s in spanish!)…. Link to bad automatic translation. =)
[tags]metasearch, relevance[/tags]
[...] Now, the question for libraries is when are we going to demand OpenSearch interfaces from our information providers? The inclusion of OpenSearch in IE7 more than gives it critical mass, but so far it seems to be just something a few progressive library-types are experimenting with. In the short term, imagine how improved our metasearch tools would be if based on fully-implemented OpenSearch feeds (with the facets and suggestions). In the long term, I can’t imagine any aspect of a library’s online services not touched by this technology. [...]
FYI:
http://libraryfind.org/
LibraryFind is…
an open source metasearch application developed by librarians for libraries, built with Ruby on Rails.
Some Current Features:
Built-in OpenURL resolver
2-click find workflow
Ability to locally index collections
Web-based administration
3-tiered caching system (to improve speed of searches)
Customizable user interface
LibraryFind® is software developed by the Oregon State University Libraries, funded in part by a grant from the State Library.