 |
 |
[ this discussion may be a bit too detailed for the general readership of code4lib; readers not interested in the upcoming WC search API may wish to skip... ] Roy, Atom/RSS are simply the container formats used to return multiple items of some kind --- I'm curious about what those items contain. In the example shown in http://worldcat.org/devnet/index.php/SearchAPIDetails#Using_OpenSearch it appears that the items are only preformatted citations, rather than, for instance, MARCXML or DC representation of records. (The SRU interface, on the other hand, appears to return MARCXML/DC.) Is this impression false and does the OpenSearch API in fact return record metadata beyond preformatted citations? (I note that your search syntax for OpenURL does not allow the choice of a recordSchema.) If so, what's the rationale for not supporting the retrieval of record metadata via OpenSearch? - Godmar On Tue, Jun 24, 2008 at 10:17 AM, Roy Tennant <[log in to unmask]> wrote: > To be specific, currently supported record formats for an OpenSearch query > of the WorldCat API are Atom and RSS as well as the preformatted citation. > Roy > > > On 6/23/08 6/23/08 • 10:18 PM, "Godmar Back" <[log in to unmask]> wrote: > > > Thanks --- let me do some "query refinement" then -- does anybody know of > > examples where record metadata (e.g., MARCXML or DC) is returned as an > > OpenSearch response? [ If I understand the proposed Worldcat API > correctly, > > OpenSearch is used only for pre-formatted citations in HTML. ] > > > > - Godmar > > > > On Tue, Jun 24, 2008 at 12:54 AM, Roy Tennant <[log in to unmask]> wrote: > > > >> I believe WorldCat qualifies, although the API is not yet ready for > general > >> release (but soon): > >> > >> <http://worldcat.org/devnet/index.php/SearchAPIDetails> > >> > >> Roy > >> > >> > >> On 6/23/08 6/23/08 € 8:55 PM, "Godmar Back" <[log in to unmask]> wrote: > >> > >>> Hi, > >>> > >>> are there any examples of functioning OpenSearch interfaces to library > >>> catalogs or library information systems? > >>> > >>> I'm specifically interested in those that not only advertise a > text/html > >>> interface to their catalog, but who include OpenSearch response > elements. > >>> One example I've found is Evergreen; though it's not clear to what > extent > >>> this interface is used or implemented. For instance, their demo > >>> installation's OpenSearch description advertises an ATOM feed, but > what's > >>> returned doesn't validate. (*) > >>> > >>> Are there other examples deployed (and does anybody know applications > >> that > >>> consume OpenSearch feeds?) > >>> > >>> - Godmar > >>> > >>> (*) See, for instance: > >>> > >> > > http://demo.gapines.org/opac/extras/opensearch/1.1/PINES/atom-full/keyword/?s > >> > e > >>> archTerms=music&startPage=&startIndex=&count=&searchLang > >>> which is not a valid ATOM feed: > >>> > >> > > http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fdemo.gapines.org%2Fop > >> > a > >>> > >> > > c%2Fextras%2Fopensearch%2F1.1%2FPINES%2Fatom-full%2Fkeyword%2F%3FsearchTerms%>> > 3 > >>> Dmusic%26startPage%3D%26startIndex%3D%26count%3D%26searchLang > >>> > >> > >> -- > >> > > > > -- >