Relevance as a percentage (originating from ​Nationaal Georegister)

Date	2009/09/03
Contact(s)	​Heikki Doeleman
Last edited	Timestamp
Status	draft
Assigned to release	2.5
Resources	The work may be done in the NGR project

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.

Proposal Type

• Type: GUI change, Core change
• App: GeoNetwork
• Module: Search results, Search engine

Links

• Email discussions: on geonetwork-devel: ​Proposals to include NGR functionality to GeoNetwork trunk
• IRC discussions: ​September 1st, 2009 on GeoNetwork's IRC channel

Voting History

• None as yet

---

Motivations

The motivations for these changes are :

1. Better usability

Proposal

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*.
In ​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.

Backwards Compatibility Issues

none

Risks

Participants

• As above