[Resent] Document boosting based on .. semantics?

Hi, [Resent: guess I sent the first before I completed my subscription, just in case it comes up twice ...] the subject may be a bit weird but I couldn't find a better way to describe a problem I'm trying to solve. If I'm not mistaken, one factor of scoring is the distance of the word with

Re: Alternate spelling suggestion (was [Resent] Document boosting based on .. semantics? )

Hi Mathieu Lecarme wrote: On a related topic, I'm also searching for a way to suggest alternate spelling of words to the user, when we found a word which is very less frequent used in the index or not in the index at all. I'm Austrian based, when I e.g. search for "retthich" (wrong spelled "re

Stemming german words

Hi, I'm currently using the GermanStemmer and it works well. However today I've found two words which get stemmed to the same stemm-word. "Suche" and "Sucht" both get stemmed to the same "such" it seems, however they've completely different meanings in german (Suche = the Search, Sucht => ad

Re: Stemming german words

they will probably add "drug" or "alcohol", etc... to the search. Ciao, Jonathan O'Connor XCOM Dublin Inactive hide details for Markus Fischer <[EMAIL PROTECTED]>Markus Fischer <[EMAIL PROTECTED]> *Markus Fischer <[EMAIL P

Different fields in the same and index and query boosting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, 1) Many different fields because of different projects? I'm accessing Lucenes index on a remote server through XML-RPC and I'ld like to use one index for completely independent search projects. The number of query requests is not that high (just

Public access to the stemmer (germanstemmer in my case)

Hi, I was wondering if there's a reason why the stemmers, e.g. GermanStemmer are not accessible from outside the lucene package. When I want to highlight the search terms, I need to know which terms have been found. Example: when searching for "Vitamine" the GermanStemmer produces "Vitami".

Creating parser query "by hand"

Hi, I currently pass the search tokens as Vector to my query function and construct the string to pass to the QueryParse.parse() by hand. StringBuffer qStr = new StringBuffer(); qStr.append("title:" + queryString.trim() + "^7 "); [...] and this append for every field I want to search in. Whe

Using one physical lucene index for multiple projects

Hi, I've about five different projects which would need to access a lucene index for searching. The projects are completely unrelated to each other however it's all about the same: indexing HTML documents. Since all these projects are also runnig inside the same hosting company, I thought ab

Re: Using one physical lucene index for multiple projects

Maik Schreiber wrote: I'm running XML-RPC to allow access to the index. My idea was that I share a SecretKey between the projects indexers and projects clients. So the indexer can only add/remove documents with his key and the client can only access documents with his key. In our projects w

Re: Using one physical lucene index for multiple projects

Maik Schreiber wrote: I'm running XML-RPC to allow access to the index. My idea was that I share a SecretKey between the projects indexers and projects clients. So the indexer can only add/remove documents with his key and the client can only access documents with his key. In our projects w

Re: Using one physical lucene index for multiple projects

Maik Schreiber wrote: Currently, I also store the SecretKey (hash of it) in the index so I know when e.g. the request comes to delete all documents I also which ones. I'm not sure if you're talking about authentication for using the XML-RPC interface here...? Multiple users can authenticate t