Hi Chris

Would it be possible to enable search result weightings, configurable per facet and (ideally) per node field?

I can image this is might be a significant change!

best wishes
scotjam

Comments

cpliakas’s picture

Status: Active » Postponed

This is a great feature request, and some of it is actually in progress. Right now, there is talk of pushing some of that functionality to Search Lucene UI, where users can have personalized results. In terms of "content bias", I am going to save that for a contributed module, as I think that functionality should be separated from the core module. The trick will be to have the field weighting available to all Lucene indexes. For example, Search Lucene API can easily index many pieces of content like the advanced help text or external HTML pages. Ideally he content bias should be able to pick up the applicable fields in those modules and add a tab to each of their settings pages to allow for content bias. Because of all of this, I am going to mark this issue as "postponed" until a more cohesive plan is formulated.

Thanks,
Chris

cpliakas’s picture

Version: 6.x-2.0-alpha2 » 6.x-2.x-dev
Assigned: Unassigned » cpliakas
Category: feature » task
Status: Postponed » Active

The core API has been reworked so that content bias is more easily achieved. After some thought, I think that content bias is important enough to move into core since the core search has a limited implementation and Apache Solr has a more complete one.

cpliakas’s picture

Status: Active » Fixed

More items can still be added, but commit #273584 adds a ton of bias settings to Search Lucene Content. Marking task as complete because the framework is set up and functional, although the functionality will be expanded.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.