RE: [search-ws] SWS Description for my SRW server

Exactly right.  There is no need
for the abstract concept of a group of records, just the individual records
themselves.

 

Ralph

 

From: Ray Denenberg,
Library of Congress [mailto:] 

Sent: Monday, April 28, 2008 4:11 PM

To: 

Subject: Re: [search-ws] SWS Description for my SRW server

 

Ralph
--

 

<item>

     
<tagpath>/srw:searchRetrieveResponse/srw:records/srw:record/srw:recordData</tagpath>

 </item>

 

We don't have an
abstract element 'item'. We have 'items' 

(which would correspond to 

     
<tagpath>/srw:searchRetrieveResponse/srw:records/</tagpath>

 

So how do you suggest we
treat this?   Define an abstract element 'item'   and
remove the abstract element "items"?

 

 

--Ray

-----
Original Message ----- 

From: LeVan,Ralph 

To:  

Sent: Thursday, April 24,
2008 4:44 PM

Subject: [search-ws] SWS
Description for my SRW server

 

With great apologies to Ashley!  I know he’s put a
great deal of work into creating the description language/schema and I’m
completely ignoring that work.  I was ordered not to look at his version
for fear it would corrupt mine.  As you can see, mine is pretty trivial,
but is sufficient to allow an OpenSearch-like client to do more than they can
currently do in OpenSearch.

 

Ralph

 

<sws>

  <databaseInfo>

    <name>Science Fiction
Database</name>

    <shortName>SciFi</shortName>

    <contact><name>Ralph
LeVan</name><email></email></contact>

    </databaseInfo>

  <requestInfo>

    <template>

     
http://orlabs.oclc.org/SRW/search/scifi?query=cql.any+%3D+%22{query}%22&version=1.1&operation=searchRetrieve&maximumRecords={maximumItems}&startRecord={startPosition}

      </template>

    <example>

     
http://orlabs.oclc.org/SRW/search/scifi?query=cql.any+%3D+%22ninja+turtles%22&version=1.1&operation=searchRetrieve&maximumRecords=10&startRecord=1

      </example>

    </requestInfo>

  <responseInfo type='xml' xmlns:srw='http://www.loc.gov/zing/srw/'>

    <numberOfItems>

     
<tagpath>/srw:searchRetrieveResponse/numberOfRecords</tagpath>

      </numberOfItems>

    <item>

     
<tagpath>/srw:searchRetrieveResponse/srw:records/srw:record/srw:recordData</tagpath>

      </item>

    <diagnostics>

     
<tagpath>/srw:searchRetrieveResponse/srw:diagnostics</tagpath>

      </diagnostics>

    </responseInfo>

  </sws>