Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Mon, 3 Jan 2011 01:31:26 -0800 (PST)
From: Amr ElAdawy <Amr.ElAdawy@etisalat.com>
To: java-user@lucene.apache.org
Message-ID: <1294047086752-2183784.post@n3.nabble.com>
In-Reply-To: <996817.46891.qm@web121702.mail.ne1.yahoo.com>
References: <1294038939049-2183420.post@n3.nabble.com>
 <996817.46891.qm@web121702.mail.ne1.yahoo.com>
Subject: Re: Search Score percentage, Should not be relative to the highest
 score
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Hi iorixxx, Thanks a lot for your reply

I had read the link and I understand the concern, however, the normalization
is happening inside lucene. Where the normalizing value is the inverse of
the maxScore.

I can alter the code to leave the original score, however it is a business
requirements to view the matching percentage. Also, the absolute score means
nothing because we wont know the exact matching score.


I am thinking of alter the core to make the normalization relative to the
number of terms, considering that the each term will score 1, so the exact
match should score 3 if there are 3 terms.

The problem for that, I dont know how to get the number of Clauses from
Query, nor the number of Terms.
Also, some exact matching results scored more than 3 !!


any ideas?
-- 
View this message in context: http://lucene.472066.n3.nabble.com/Search-Score-percentage-Should-not-be-relative-to-the-highest-score-tp2183420p2183784.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org