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
|