and counting...
--
--
Kyle Banerjee
Digital Services Program Manager
Orbis Cascade Alliance
[EMAIL PROTECTED] / 541.359.9599
The typical use case, though, is for the featured document to be on top only
for certain queries. Like in an intranet where someone queries 401K or
retirement or similar, you want to feature a document about benefits that
would otherwise rank really low for that query. I have not be able to
In the near future, you can do a real query-time boost (score multiplication)
by another field or function
https://issues.apache.org/jira/browse/SOLR-334
And even quickly update all the values of the field being used as the boost:
https://issues.apache.org/jira/browse/SOLR-351
Thanks, all
Howdy all,
We are attempting to provide access to about 8 million records of
highly variable quality and length. In a nutshell, we are trying to
find a way to deprioritize suspect records without discriminating
against useful records that happen to be short. We do not wish to
eliminate suspect
If you know at index time that the document is shady, the easiest way
to de-emphasize it globally is to set the document boost to some
value other than one.
doc boost=0.5...
I considered that, but assumed we'd get the values wrong at first and
have to do a lot of tinkering before we got it
I know I'm missing something really obvious, but I'm spinning my
wheels figuring out how to eliminate lengthNorm from the calculations.
The specific problem I'm trying to solve is that naive queries are
resulting in crummy short records near the top of the list. The
reality is that the longer
