On 6/23/06, Bernhard Eversberg <ev_at_biblio.tu-bs.de> wrote:
> Mike Rylander wrote:
> >> >> >
> >> >> Again, who does it, and why not?
> >> >
If you're going to complain about something not being there, let's
quote the entire block of text, eh?
>> > Again, a relational database can contain keyword indexes either
>> > through full text indexing a column or using appropriate business
>> > logic and/or a stored procedures to shred the information and
>> > store the data in a table.
... and interpreting your later comment in /that/ context ...
> >> >
> >> > Evergreen, for one. :)
> >> >
> >> Where can I see it?
> >>
> >
> > http://open-ils.org
> > http://demo.gapines.org/
> >
>
> pardon me, but I cannot find anything that looks like an index there.
> Even, if I enter a term that's not in the database, there's no helpful
> hint of any kind but "Zero hits were returned for your search."
> That is not good enough, or so I think, for "next generation". What I
> expect is not "Did you mean xyz" with a non-relevant xyz more often than
> not, but an A-Z list of terms, opened at the position where my term
> would have to be but is not. So I can see that it isn't there but
> maybe another spelling that escaped the helpful software.
Much of this is thread, and specifically my response to your "who does
this" (which was in response to "you could use an RDBMS"), was not
about an A-Z, back of the book, physical "Index Of Contents", but an
implementation detail regarding the use of a relational database that
is used to search a catalog. I'd ask you to refrain from putting
words in my mouth, such as (to paraphrase) "Evergreen drops you into a
browse list when you misspell something so badly that the the spell
checker can't help you out" -- which it most certainly doesn't, and
more than likely never will.
However, I will follow your track off course if you like. If you
search for "asdflkjdfqw" in Google, or any library catalog, you will
never get any results -- including a USEFUL browse list.
Look, I'm as guilty as anyone about having pet features, but we all
need to be careful when saying X or Y does or doesn't do Z, because
there may never have been a claim of such. And always remember the
sage wisdom of one (according to the #code4lib IRC channel bot, in any
case) David Fiander, "Working code always wins."
>
> B. Eversberg
>
--
Mike Rylander
mrylander_at_gmail.com
GPLS -- PINES Development
Database Developer
http://open-ils.org
Received on Fri Jun 23 2006 - 09:37:30 EDT