Skip
repetitive navigational links
L-Soft  -  Home of  the  LISTSERV  mailing list  manager LISTSERV(R) 14.5
Skip repetitive navigational links
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (January 2005)Back to main ZNG pageJoin or leave ZNGReplyPost a new messageSearchProportional fontNon-proportional fontLog in
Date:         Fri, 7 Jan 2005 13:10:34 -0000
Reply-To:     "Z39.50 Next-Generation Initiative" <[log in to unmask]>
Sender:       "Z39.50 Next-Generation Initiative" <[log in to unmask]>
From:         "Matthew J. Dovey" <[log in to unmask]>
Subject:      Re: Adlib Base profile
Comments: To: "Z39.50 Next-Generation Initiative" <[log in to unmask]>
Content-Type: text/plain; charset="us-ascii"

> What we really want is, in order of largest to smallest. > > anyField (any field in the underlying data, indexed or not) > anyKnown (any field indexed, not necessarily in CQL) > anyIndex (any field with a CQL Index == current cql.anywhere) Do we still need server-choice? I'd always interpreted the different between this and anywhere/anyIndex to be that anywhere would search all indexes whereas serverchoice would search only one index (somehow appropriately or inappropriate chosen by the server). Personally I'd like to see it go - I don't want any indeterminate "and the server will do the appropriate thing" in SRW ;-) Matthew


Back to: Top of message | Previous page | Main ZNG page

LISTSERV.LOC.GOV CataList email list search Powered by LISTSERV email list manager