Changes between Version 1 and Version 2 of RelevancePercentage


Ignore:
Timestamp:
Sep 3, 2009, 6:13:00 AM (15 years ago)
Author:
heikki
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RelevancePercentage

    v1 v2  
    88|| '''Resources''' || The work may be done in the NGR project ||
    99
    10 == Overview ==In standard !GeoNetwork search results can be ordered by relevance. This is based on the relevance score that the Lucene search engine gives to each item in the search results. However it is not shown to the user what the relevance score for each result *is* or how they compare between each other.[[BR]][[BR]]
     10== Overview ==
     11
     12In standard !GeoNetwork search results can be ordered by relevance. This is based on the relevance score that the Lucene search engine gives to each item in the search results. However it is not shown to the user what the relevance score for each result *is* or how they compare between each other.[[BR]][[BR]]
    1113
    1214=== Proposal Type ===
     
    3436In standard !GeoNetwork search results can be ordered by relevance. This is based on the relevance score that the Lucene search engine gives to each item in the search results. However it is not shown to the user what the relevance score for each result *is*.[[BR]]
    3537In [http://nationaalgeoregister.nl NGR] the relevance score is displayed with each search result. Because the Lucene score is an unattractive float between 0 and 1, the relevance score is normalized such that the highest score from the search results is set to 100, and all other results' scores are calculated relative to that.[[BR]][[BR]]
     38This proposal is somewhat controversial, as people may feel that scoring "100%" to the highest ranking result is misleading. An alternative could be to simply show the (rounded) Lucene relevance ranking. And it appears that many people poorly understand the nature of Lucene's relevance ranking, thinking that the calculated relevance of one search request's result could be compared to that of another search request's result (it *can't*) or that it naturally tallies with people's innate idea of what is and what isn't relevant, which is of course also not always the case. So if you don't like it, simply vote against this! [[BR]][[BR]]
    3639[[Image(ngr.relevance.percentage.png)]][[BR]]
    3740[[BR]][[BR]]