Changes between Initial Version and Version 1 of proposals/DocumentAndFieldBoosting

Timestamp:

12/20/11 02:20:02 (13 years ago)

Author:

fxp

Comment:

--

proposals/DocumentAndFieldBoosting

@@ +1 @@
+= Virtual CSW endpoints =
+
+|| '''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).
+
+
+=== 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 (see #336).
+
+Add the capability to set field and document boosting as explained in ticket #708.
+
+
+=== Backwards Compatibility Issues ===
+The default configuration does not set any boosting (current score do not change).
+
+== Risks ==
+
+== Participants ==
+ * Francois Prunayre