LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  December 2004

ZNG December 2004

Subject:

Re: Adlib Base profile

From:

Mike Taylor <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Thu, 16 Dec 2004 00:02:41 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (68 lines)

> Date: Wed, 15 Dec 2004 23:15:31 +0000
> From: Dr Robert Sanderson <[log in to unmask]>
>
> >> I think that's exactly what cql.anywhere means.  Search all
> >> indexes that you know about, but you can't be expected to search
> >> indexes that you don't
> >
> > Well, I will leave it to the profile author to say whether that
> > was what he meant.  I read the Adlib-specific definition to mean
> > that they wanted "anywhere" to mean "in any of the Adlib access
> > points only".
>
> Then I would suggest:
>
> adlib.anywhere   Search in any of the indexes defined in the adlib context
>                   set.

Sounds right to me -- if that's what the writer did mean.

> > For Adlib, there _is_ an implementation difference between (the
> > putative) cql.record access point on cql.anywhere. in that the latter
> > makes use of all the indexes that are to hand, but the former makes a
> > physical scan of all records, so it can even find the term in fields
> > that are not indexed.  As I implied, not every server will implement
> > this (which is fine) but it does seem like a useful distinction for
> > those that do.
>
> cql.anyField ?  I don't like cql.record as a name, as to me that would
> imply that a string search should be matched against the entire record,
> rather than any subfield within the record.

Agreed -- your name is better,

> Also, if the text isn't indexed at all, how do you determine where to
> start matching and where to end?

I don't understand.  Whatever you might otherwise have done at
indexing time, you just do at search time instead.  Run-time
performance will suffer, but the pay-off is of course smaller index
files.

> >>> This is _not_ what "=" means in CQL.  It means that the term is
> >>> word-structured, irrespective of the index being searched, unless
> >>> overridden by a relation modifier.
> >>
> >> I disagree, Mike.  It means, currently, exact equality, but does not
> >> say how equality is to be determined.
> >
> > Au contraire.  This is precisely the difference between "=" and
> > "exact".
>
> =/cql.number  must surely mean exact numeric equality?

Er.

Oh, look!  A badger!

 _/|_    _______________________________________________________________
/o ) \/  Mike Taylor  <[log in to unmask]>  http://www.miketaylor.org.uk
)_v__/\  "When you are young, you enjoy a sustained illusion that
         sooner or later something marvelous is going to happen [...]
         But it isn't like that at all.  But if it isn't, where did
         the idea come from?" -- Brian Aldiss, _Helliconia Summer_

--
Listen to free demos of soundtrack music for film, TV and radio
        http://www.pipedreaming.org.uk/soundtrack/

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

July 2017
October 2016
July 2016
August 2014
February 2014
December 2013
November 2013
October 2013
February 2013
January 2013
October 2012
August 2012
April 2012
January 2012
October 2011
May 2011
April 2011
November 2010
October 2010
September 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
May 2009
April 2009
March 2009
February 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager
https://listserv.loc.gov/cgi-bin/wa?A2=ind0412&L=ZNG&D=0&P=54263
listserv.loc.gov
CC-MAIN-2024-10
52152
application/http; msgtype=response
sha1:CZPVTSTFRQCFNEEIECE2NT24PRIVBTQK
<urn:uuid:1c4880ad-710c-4631-a618-d419ed8bc43d>
2024-02-25T14:21:49Z
104.16.55.16
text/html
sha1:OKVXXZSOBVIRFGRACMEMIZLUTDTGVVCY
<urn:uuid:68ac39b3-d78b-4b01-9e03-db1a1a87d63c>
https://listserv.loc.gov/cgi-bin/wa?A2=ind0412&L=ZNG&D=0&P=54263
response
<urn:uuid:ae5adaa3-4c06-4e8c-a1e3-7af5a76a4c11>
isPartOf: CC-MAIN-2024-10
publisher: Common Crawl
description: Wide crawl of the web for February/March 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-239
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/