>Before making new database designs I think it is important to state the goals
>first. Let the market/user requirements determine the actual design.
Sounds good to me. I'll add a few (many stolen from TODO.html or the
feature pile in the bug database).
Andrew's:
>* phrase searching
>* fuzzy searching (basically as it is now)
>* use of "+" or "-" as prefix to search words (ala altavista)
>* use of "near" as a method to determine relations between search words
>* cross platform (unix, nt)
>* ability to search only in specific areas of documents (title, headers, etc)
>* better relevance ranking
>* faster results generation for searches returning many hits
Mine:
* Collections of databases
* Parallel indexing and searching (no need for alternate files or htmerge)
* Multithreading support (some sort of locking for writes)
* Removing duplicate documents
* Referer links (e.g. AltaVista-style link:)
* Search for "more like" or "similar to" (a la Excite)
* On-the-fly editing of word factors (without needing to rebuild the db)
>is a big departure from how ht://Dig was originally developed, but I have
>learned a lot since I started on it! :-)
Well let's put all those lessons to use! :-)
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
