I found the "field weights" section at admin/settings/apachesolr/query-fields somewhat confusing, since I did not understand at all how the boosting works with different types of fields. In particular, if you "omit" the body field, text in the node body can still be searched if it appears within an HTML tag (such as <h2>) that has a weight assigned to it.
Implementation details aside, I think human-readable descriptions for the fields would help here (not sure how hard this is since I'm not sure about the various origins of all the fields). Also, I think phrasing things in terms of "points" rather than "weights" might make more sense. For example:
Specify here which fields are more important when searching. Give a field more points to make it more important. Text that does not accumulate any points below will not be searched.
If text appears in the node body, give it:
* 21 points
* 13 points
* ...
* 1 point
* No points
If text is enclosed in <h2> or <h3> tags, give it:
* 21 points
* 13 points
* ...
* 1 point
* No points
(I'm assuming here that Lucene treats the weights as additive, or at least close enough to additive that it makes sense to refer to them this way.)
Does this make sense and sound like a good idea?
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | admin-clarify-365495-8.patch | 10.6 KB | pwolanin |
| #7 | admin-clarify-365495-7.patch | 9.64 KB | pwolanin |
| #6 | admin-clarify-365495-6.patch | 8.95 KB | pwolanin |
| #5 | bias-clarify-365495-5.patch | 6.43 KB | pwolanin |
| #3 | bias-clarify-365495-2.patch | 6.59 KB | pwolanin |
Comments
Comment #1
pwolanin commentedmarked as duplicate: #450836: Content Bias settings offends UX Gods
Comment #2
janusman commentedRelated (partial overlap): #378376: Improve (reorganize/clarify) admin screens
Comment #3
pwolanin commentedOk, will have to look - just started on some of the text.
Comment #4
pwolanin commentedComment #5
pwolanin commentedThis one doesn't get everything, but perhaps is commitable as an interim.
Comment #6
pwolanin commentedQuick implementation of field name mapping too.
Comment #7
pwolanin commentedmove the bulk of the mapping function to the admin.inc file.
Comment #8
pwolanin commentedcommitted to 6.x