Date:         Wed, 21 Aug 2002 09:43:14 -0400
Reply-To:     "Z39.50 Next-Generation Initiative" <[log in to unmask]>
Sender:       "Z39.50 Next-Generation Initiative" <[log in to unmask]>
From:         "Larry E. Dixson" <[log in to unmask]>
Subject:      Re: Indexes
Comments: To: "Z39.50 Next-Generation Initiative" <[log in to unmask]>
In-Reply-To:  <[log in to unmask]>
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 21 Aug 2002, Robert Sanderson wrote:

> Two questions/comments on indexes:
>
> *  Can we come up with a standard set of naming conventions for indexes
> please?  At the moment DC has titleString whereas Bath has TitleExact.
>
> The 'send the same query to everyone' style will be much easier if they're
> all using the same conventions, regardless of whether they call them DC or
> Bath or anything else.  If there's a convention already established then
> people will just follow it rather than making their own.
>
> My (easily swayed) preference is 'fooWord' and either 'foo' or 'fooExact'.

Rob,
This has been bothering me since you mentioned this in a previous email
message.  I looked back at my notes from the meeting and, as usual,
they're not complete.  However, I do have the following circled (meaning
that I thought we had agreed):

---------------------------------------------------
    dc.<field>
    dc.<field>Word

    The above will be used for all except "dc.date".
---------------------------------------------------

That would yield "dc.title" and "dc.titleWord".  I also thought that
we had discussed using this same style for the Bath searches. (Alas, this
is not documented in my notes -- what do you have in your "official"
notes?)  However, I did note that the "unanchored phrase" searches in Bath
Functional Area C (e.g., "Title Search - Unanchored Phrase") could be
specified with search terms carrying the truncation symbol as the
first and last characters of the term.  (Whatever we decide, we should
probably add these Functional Area C Indexes to our list of Bath indexes.)

The problem I'm having is that I no longer remember how we thought we
could distinguish between "first-characters-in-field" and
"first-words-in-field" searches in Bath.  In other words, what would
we have to put into the search term in order to indicate "incomplete
subfield"?

bath.titleExact            would be   bath.title="search term"
bath.titleFirstCharacters  would be   bath.title="search term*"
bath.titleFirstWords       would be   bath.title="<what?>"

Were we specifying the "firstWords" search with proximity?

Larry

>
>
> *  Are index/index set names case sensitive or not?
>
> Are 'Title' and 'title' the same index? I looked but couldn't find it in
> the documentation.  For example, bath.titleWord but bath.TitleExact are
> listed on the Bath page.  If they're case sensitive then this should be
> standardised.
>
> Rob
>
> --
>       ,'/:.          Rob Sanderson ([log in to unmask])
>     ,'-/::::.        http://www.o-r-g.org/~azaroth/
>   ,'--/::(@)::.      Special Collections and Archives, extension 3142
> ,'---/::::::::::.    Twin Cathedrals:  telnet: liverpool.o-r-g.org 7777
> ____/:::::::::::::.              WWW:  http://liverpool.o-r-g.org:8000/
> I L L U M I N A T I



------------------------------------------------------------
Larry E. Dixson                    Internet:    [log in to unmask]
Network Development and MARC
   Standards Office, LM639
Library of Congress                Telephone: (202) 707-5807
Washington, D.C.  20540-4402       Fax:       (202) 707-0115