> > 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.
> > My (easily swayed) preference is 'fooWord' and either 'foo' or 'fooExact'.
> 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):
I have the same thing in my notes (which you all have anyway)
> 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
Which is fine by me :)
> 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
> 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?
That would make sense, but is pretty ugly for a term which has many words.
bath.titleWord="search" prox/word/1 bath.titleWord="term" prox...
As we have ""ed terms, isn't firstWords actually:
bath.title="search term *"
as the whitespace is meangingfull?
> > * Are index/index set names case sensitive or not?
> > Are 'Title' and 'title' the same index? I looked but couldn't find it in
My preference is for case insensitive, especially for situations when
users type in their own CQL, or typos in Specification documents :)
,'/:. Rob Sanderson ([log in to unmask])
,'--/::(@)::. 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