Deboosts not working as intended about universal-recommender HOT 2 OPEN

A quick analysis shows no bug. If you set a 0 < bias < 1 it will increase the scores over removing the fields and therefore having no match at all for that field because but because you are adding a new match, which is additive you see some small increase. In other words the fact of adding the field will increase over no field but a bias <1 will make the match arbitrarily small, approaching 0, which would be equal to omitting the field. Another way to say this is that the deboost is in comparison to any other form of bias.

So given the presentence of the field < 1 is deboosting.

Anyway this is as designed. i suppose what you want is a new feature, which is to move the field to the "should_not" clause of the ES query with it's own bias?

from universal-recommender.

Let me try to explain the deboost better.

Imagine 2 fields: housewares, and electronics. If you want to boost electronics and deboost housewares you would apply bias = 1.5 to electronics and 0.5 to electronics. then houseware will be ranked higher that electronics.

Another thing you can do is apply a boost of 0 to housewares and none will be shown, they will all be excluded.

I don't think these work for your needs so understand the issue but anyway, it's the way things work today.

from universal-recommender.