Delaying the autosuggest until three or four characters have been
entered should save some time.
Unfortunately, the search results aren't very digestible. The query
term is matched anywhere in the heading, and only 30 results are
returned per page. So, for example, the first page of a search for
"doc*":
http://id.loc.gov/authorities/search/?q=doc*
doesn't return any results that actually start with "doc" (" Act of
state doctrine", "Adventists--Doctrines",
"Agriculture--Documentation", etc).
Ben
On Mon, Dec 7, 2009 at 11:21 AM, Doug Chestnut <[log in to unmask]> wrote:
> mod_cache might help, assuming that performance gets better as your
> query string grows.
>
> --Doug
>
> On Mon, Dec 7, 2009 at 11:14 AM, Ethan Gruber <[log in to unmask]> wrote:
>> It doesn't seem very efficient. It is taking me at least 30 seconds to load
>> a page of 'a*' in http://id.loc.gov/authorities/search/
>>
>> On Mon, Dec 7, 2009 at 11:05 AM, Houghton,Andrew <[log in to unmask]> wrote:
>>
>>> > From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
>>> > Winona Salesky
>>> > Sent: Monday, December 07, 2009 11:00 AM
>>> > To: [log in to unmask]
>>> > Subject: Re: [CODE4LIB] Auto-suggest and the id.loc.gov LCSH web
>>> > service
>>> >
>>> > Quoting Ethan Gruber <[log in to unmask]>:
>>> >
>>> > > I have a need to integrate the LCSH terms into a web form that uses
>>> > > auto-suggest to control the vocabulary. Is this technically possible
>>> > with
>>> > > the id.loc.gov service?
>>>
>>> Why can't you just add a "*" to the end of the data in your search form
>>> and send the request to the id.loc.gov search, per:
>>>
>>> <http://id.loc.gov/authorities/techcenter/searching.html>
>>>
>>> then parse the response?
>>>
>>>
>>> Andy.
>>>
>>
>
--
Benjamin Florin
Technology Assistant for Blended Education
Simmons College GSLIS
617-521-2842
[log in to unmask]
