[Web4lib] Re: OpenSearch, Koha, and Library Catalogs [SRW/U]
Ross Singer
ross.singer at library.gatech.edu
Mon Jul 25 10:09:24 EDT 2005
Mike, I think you're missing my point.
What does the "remote" (client) site do with this page:
http://z3950.loc.gov:7090/voyager?query=hemingway&startRecord=1&maximumRecords=1&recordSchema=dc&version=1.1&operation=searchRetrieve
Imagine a larger result set, with multiple "types" of results (some
monographs, some electronic, some other types) where your metadata
results might vary?
OpenSearch requires a "title" and "url" for each result and an option
description.
The other thing I note is that SRU requires an SRW/U server -- which,
frankly, probably means only bibliographic data will be searched. I
realize that we're talking about bibliographic data in this case, but it
would be very narrow minded to limit ourselves only to that.
Also, I want to reiterate the fact that our OpenSearch implementation
/is merely transforming queries to and from our SRU implementation/. A9
does not support SRU, so what do we do? Boycott them? Or adapt our
services to work with them?
-Ross.
Mike Taylor wrote:
>>Date: Mon, 25 Jul 2005 09:42:12 -0400
>>From: Ross Singer <ross.singer at library.gatech.edu>
>>
>>The advantage that I see to opensearch is that it is /solely/ a
>>discovery protocol. With SRW/U, you have to then figure out how to
>>display full records, variants in regards to metadata schemas, etc.
>>In essence, a very robust client needs to be developed.
>>
>>
>
>Eh? You've lost me. WHat's complex about the SRU client at
> http://sru.miketaylor.org.uk/
>?
>
> _/|_ ___________________________________________________________________
>/o ) \/ Mike Taylor <mike at miketaylor.org.uk> http://www.miketaylor.org.uk
>)_v__/\ "Specifications are for the weak and timid!" -- Klingon
> Programming Mantra
>
>--
>Listen to free demos of soundtrack music for film, TV and radio
> http://www.pipedreaming.org.uk/soundtrack/
>
>
>
>
More information about the Web4lib
mailing list