Changes between Version 1 and Version 2 of proposals/DocumentAndFieldBoosting


Ignore:
Timestamp:
Dec 20, 2011, 2:27:10 AM (13 years ago)
Author:
fxp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • proposals/DocumentAndFieldBoosting

    v1 v2  
    1313The main objective of this proposal is to be able to customize default Lucene scoring in order to promote certain types of records.
    1414
    15 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).
    16 
     15A 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).
     16For example, having a catalogue with :
     17 * urban atlas (series)
     18 * urban atlas for Paris (dataset)
     19 * urban atlas for London (dataset)
     20 * other records (which may contains urban atlas in other fields like abstract).
     21while 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 :
     22 1. urban atlas (series)
     23 1. other records (which may contains urban atlas in abstract).
     24 1. urban atlas for Paris (dataset)
     25 1. urban atlas for London (dataset)
    1726
    1827=== Proposal Type ===
    1928 * '''Type''': Core Change
    2029 * '''App''': !GeoNetwork
    21  * '''Module''': LuceneConfig
     30 * '''Module''': !LuceneConfig
    2231
    2332=== Links ===
    … …  
    3342== Proposal ==
    3443
    35 Document and field boosting are applied at index time. See boosting query to do boosting at search time (see #336).
     44Document and field boosting are applied at index time (See boosting query to do boosting at search time in #336).
    3645
    37 Add the capability to set field and document boosting as explained in ticket #708.
     46See ticket #708 for configuration and patch.
     47
     48This 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.
    3849
    3950