[Yazlist] baffled by cql, or maybe rec.id

Mike Taylor mike at indexdata.com
Sat Mar 26 01:40:59 CET 2011


On 26 March 2011 00:34, Enrico Silterra <es287 at cornell.edu> wrote:
> here is the interaction, connecting to yaz proxy,
> which connects to a voyager z39.50 server.
>
> yaz-client -a apdu.log lxxxxxx:9090/voyager
> Connecting...OK.
> Sent initrequest.
> Connection accepted by v3 target.
> ID     : 34
> Name   : Voyager LMS - Z39.50 Server (YAZ Proxy)
> Version: 2007.1.1/1.3.6
> Options: search present
> Elapsed: 1.674038
> Z> querytype cql
> Z>  f rec.id=1001 or rec.id=1002
> Sent searchRequest.
> Received SearchResponse.
> Search was a success.
> Number of hits: 10000
> records returned: 0
> Elapsed: 7.503895
> Z> quit
>
>
> initRequest {
>   protocolVersion BITSTRING(len=1) 111
>   options BITSTRING(len=2) 11101001-1010001
>   preferredMessageSize 1048576
>   maximumRecordSize 1048576
>   implementationId '81'
>   implementationName 'YAZ'
>   implementationVersion '3.0.52 e687cb7eb87c841f0d1a374174d51d30371f2d97'
> }
> initResponse {
>   protocolVersion BITSTRING(len=1) 111
>   options BITSTRING(len=1) 11
>   preferredMessageSize 32768
>   maximumRecordSize 1048576
>   result TRUE
>   implementationId '34'
>   implementationName 'Voyager LMS - Z39.50 Server (YAZ Proxy)'
>   implementationVersion '2007.1.1/1.3.6'
> }
> searchRequest {
>   smallSetUpperBound 0
>   largeSetLowerBound 1
>   mediumSetPresentNumber 0
>   replaceIndicator TRUE
>   resultSetName 'default'
>   databaseNames {
>       'voyager'
>   }
>   {
>       query choice
>       type_104 {
>           OID: 1 2 840 10003 16 2
>           type_104 choice
>           {
>               'rec.id=1001 or rec.id=1002'
>           }
>       }
>   }
> }
> searchResponse {
>   resultCount 10000
>   numberOfRecordsReturned 0
>   nextResultSetPosition 1
>   searchStatus TRUE
>   presentStatus 0
> }

That is extremely strange.  As you may know, the Library of Congress's
Z39.50 server is implemented by the same combination -- YAZ Proxy in
front of a Voyager catalogue -- and that works just fine, as you can
see in the transcript below.

I can only think there must be some misconfiguration in the specific
YAZ Proxy or Voyager installation of the particular server you're
trying to work with.  Sorry if that's not very helpful.

-- Mike.




cartney:photos mike$ yaz-client z3950.loc.gov:7090/voyager
Connecting...OK.
Sent initrequest.
Connection accepted by v3 target.
ID     : 34
Name   : Voyager LMS - Z39.50 Server (YAZ Proxy)
Version: 2007.2.0/1.2.1.1
Options: search present
Elapsed: 0.423290
Z> querytype cql
Z> f rec.id=1001
Sent searchRequest.
Received SearchResponse.
Search was a success.
Number of hits: 0
records returned: 0
Elapsed: 0.165135
Z> f rec.id=1001 or rec.id=1002
Sent searchRequest.
Received SearchResponse.
Search was a success.
Number of hits: 1
records returned: 0
Elapsed: 0.179830
Z> f rec.id=1001 or rec.id=1002 or rec.id=1003
Sent searchRequest.
Received SearchResponse.
Search was a success.
Number of hits: 1
records returned: 0
Elapsed: 0.145695
Z> f rec.id=1001 or rec.id=1002 or rec.id=1003 or rec.id=1004
Sent searchRequest.
Received SearchResponse.
Search was a success.
Number of hits: 1
records returned: 0
Elapsed: 0.156986
Z> f rec.id=1001 or rec.id=1002 or rec.id=1003 or rec.id=1004 or rec.id=1005
Sent searchRequest.
Received SearchResponse.
Search was a success.
Number of hits: 2
records returned: 0
Elapsed: 0.197544
Z>



More information about the Yazlist mailing list