Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of samuelgmartinez@gmail.com
 designates 209.85.220.176 as permitted sender)
MIME-Version: 1.0
Date: Mon, 14 Nov 2011 10:40:30 +0100
Message-ID: 
 <CAMNCBP7mGTRd6M-wK6eXy6BLajOtHkwOcU+mmrcE2vJuSex8_A@mail.gmail.com>
Subject: How to determine result quality
From: =?ISO-8859-1?Q?Samuel_Garc=EDa_Mart=EDnez?= <samuelgmartinez@gmail.com>
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=20cf3071c8805bd46604b1aea91d

--20cf3071c8805bd46604b1aea91d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi list,

I have been searching about score normalization few days (now i know this
can't be done) in Lucene using this list, wiki, blogposts, etc. I'm going
to expose my problem because I'm not sure that score normalization is what
our project need.

*Background*:
  In our project, we are using Solr on top of Lucene with custom
RequestHandlers and SearchComponents. For a given query, we need to detect
when a query got poor results to trigger different actions.

*Assumptions*:
  Inmutable index (once indexed, it is not updated) and Same query tipology
(dismax qparser with same field boosting, without boost functions nor boost
queries).

*Problem*:
  We know that score normalization is not implementable. But is there any
way to determine (using TF/IDF and boost field assumptions) when search
results match quality are poor?

*Example: *We've got an index with science papers and other one with
medcare centre's info. When a user query against first index and got poor
results (inferring it from score?), we want to query second index and merge
results using some threshold (score threshold?)

Thanks in advance
--=20
Un saludo,
Samuel Garc=EDa.

--20cf3071c8805bd46604b1aea91d--