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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  May 2002

ZNG May 2002

Subject:

Re: revised Bath/CQL searches

From:

Alan Kent <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Tue, 21 May 2002 11:06:01 +1000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (86 lines)

On Mon, May 20, 2002 at 05:18:07PM -0400, Ray Denenberg wrote:
> I've overhauled the earlier draft of Bath/CQL
> searches, based on the revised profile draft as
> well as Joe and Ralph's comments (and some
> discussion within the srw group).
>
> http://www.loc.gov/z3950/agency/zing/bath-prefixes.html
>
> --Ray

Putting a previous suggestion I have made in context here, it would
seem more logical/consistent to me to define the full 6 attributes
(to be Bath conformant), but then (like you have done with '?')
make comments that "a ? at the end of the search term means the
'do not truncate' attribute value should be replaced by 'right truncation'
attribute value.

Similarly for relation - include 'equals' in the list, and if someone
specifies '>' etc, then replace the 'equals' attribute value in the list.

This is what I had meant by saying "lets define a new concept of
'operators' for concepts such as relation, truncation, and overlaps
(GEO profile) where the attribute list of the operator is added
to the search term attribute list. If an existing OID/attribute-type
pair has a value, then it should be replaced by the operator's value
for that OID/attribute-type pair." (Oh, I think I said this on the
ZeeRex list, not this ZiNG list).

To make it a bit more concrete:


Index Names
===========

1. bath.authorWord (can be used with relation(?) and truncation operators)

    Attribute Type Attribute Values Attribute Names
    -------------- ---------------- ---------------
    Use (1) 1003 author
    Relation (2) 3 equals
    Position (3) 3 any position in field
    Structure (4) 2 word
    Truncation (5) 100 do not truncate
    Completeness (6) 1 incomplete subfield

... etc ...

Operators
=========
(Note: defined at database level, not named index level)

1. Less than

    Attribute Type Attribute Values Attribute Names
    -------------- ---------------- ---------------
    Relation (2) 1 less than

2. Less Than or Equal To

    Attribute Type Attribute Values Attribute Names
    -------------- ---------------- ---------------
    Relation (2) 2 less than or equal to

... etc ...

6. Right Truncation

    Attribute Type Attribute Values Attribute Names
    -------------- ---------------- ---------------
    Truncation (5) 1 right truncation

... etc ...


The above tables all use the Bib-1 OID of course. For a GEO profile
database, the GEO attribute set might be used instead (it has additional
operators for 'overlapping regions' etc). For a GEO database, really
want to use the GEO attribute set relation and truncation attributes
(GEO made a copy of all the Bib-1 attributes then extended them - overlaps
is a GEO relation attribue value). To avoid CQL being tied to Bib-1,
I propose that CQL be tied to operator *names* where the binding of
operator names to attribute lists be database specific (in exactly the
same way that index names are bound to attribute lists per database).

Alan

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