I have been thinking about Google Onebox technology, "next
generation" library catalogs, and interpreting user queries.
Specifically, I think the techniques behind Google Onebox technology
could easily be implemented in "next generation" library catalogs.
Google Onebox [1, 2] is a technique for providing enhanced services
against a locally implemented Google Appliance. It is also
implemented against the Google index itself. Through the Onebox
technique, Google looks at the shapes of queries and passes them off
to other, outside search engines combining the results with typical
index results. Many queries have particular patterns. Many of these
are defined by Google itself. [3] I have begun creating a Onebox for
our local Google Appliance. Enter a couple of words. By default it
searches the local personnel (LDAP) directory, and if a match is
found it returns a name, email address, and telephone number. If
nothing is found, then no harm done.
Similar things could be done against library-related indexes. Does
the query look like an ISBN number? Do in ISBN number search. Does
the query fit a name in your authority list? Return an authority
record. Does the query look like a citation? Find the article. Is
there a comma between the first and second word, then consider
changing the query on the fly to an author search.
The power of this technique is two-fold. One, it does not necessitate
the inclusion of all your content in a single index, although that is
something I advocate. Two, the technique allows you to bring back
answers instead of pointers to answers. Instead of bringing you back
a HTML page that night contain the email address and telephone
number, it returns those things directly.
In short, I think we should consider looking at the shapes of queries
before blindly sending them off to our indexes for searching. Instead
we can (should) look at the queries first, combine what we see with
our professional judgment, and possibly enhance or redirect the query
accordingly.
[1] Google Onebox design principles - http://tinyurl.com/4nvahr
[2] Google Onebox developer's guide - http://tinyurl.com/2w2qkr
[3] Cool Google queries - http://tinyurl.com/9k4nd
--
Eric Lease Morgan
University of Notre Dame
Received on Fri May 02 2008 - 14:48:55 EDT