Document and Field boosting
| Date | 2011/12/20 |
| Contact(s) | François Prunayre |
| Last edited | |
| Status | done |
| Assigned to release | 2.7.0 |
| Resources | Available |
| Ticket # | #708 |
Overview
The main objective of this proposal is to be able to customize default Lucene scoring in order to promote certain types of records.
A common use case could be to promote series and not promote datasets part of a series (the relation navigation will drive user from series to children). For example, having a catalogue with :
- urban atlas (series)
- urban atlas for Paris (dataset)
- urban atlas for London (dataset)
- other records (which may contains urban atlas in other fields like abstract).
while searching for "urban atlas", the order of the results will depends on the content of each records. With this proposal, catalogue administrator will be able to give rules to promote series and records not part of a series for example. Then the results will be :
- urban atlas (series)
- other records (which may contains urban atlas in abstract).
- urban atlas for Paris (dataset)
- urban atlas for London (dataset)
Proposal Type
- Type: Core Change
- App: GeoNetwork
- Module: LuceneConfig
Links
- Documents:
- Email discussions:
- Other wiki discussions:
Voting History
- Vote proposed by François Prunayre on 2011/12/20, result was ...
Proposal
Document and field boosting are applied at index time (See boosting query to do boosting at search time in #336).
See ticket #708 for configuration and patch.
This feature has to be used by expert users to alter default search behavior scoring according to catalogue content. It needs tuning and experimentation to not promote too much some records.
Backwards Compatibility Issues
The default configuration does not set any boosting (current score do not change).
Risks
Participants
- Francois Prunayre
Funded by EEA
