Well, as Hoss suggested, I have implemented my own function
(ValueSourceParser+ValueSource) :)
It's a very simple function which receives a parameter, the userId, and
returns a float value depending (with a switch-case structure just for this
demo) on it.
With this approach now I can boost (i.e.
Hi!
Although more than 1 year has passed, could I ask you, Parvin, what was your
final approach?
I have to deal with a similar problem
(http://lucene.472066.n3.nabble.com/Combining-Solr-score-with-customized-user-ratings-for-a-document-td4040200.html),
maybe a bit more difficult because it's a
Hi Tim!
Thank you for bringing in some light ;)
I have read your slides (in fact, I had already read them in the last days)
but I'm still missing something.
So, let's see...
As I see (and I may be wrong) Solr's external file fields are some kind of
docID, score maps, aren't them? I understand
Á_o wrote
As I see (and I may be wrong) Solr's external file fields are some kind of
lt;docID, scoregt; maps, aren't them?
Actually I was wrong ;)
The key does not have to be necessarily the docID. It can be some other
field. Anyway, even in that case, it's still a 'docKey' which I can't
Well, thinking a bit more, the second solution is not practical.
If Solr retrieves, say, 1.000 documents, I would have to navigate through
ALL (maybe less with some reasonable upper limit) of them to recalculate the
scores and reorder them according to the new score although the Web App is
going
Hi:
I am working on a proyect where we want to recommend our users products
based on their previous 'likes', purchases and so on (typical stuff of a
recommender system), while we want to let them browse freely the catalogue
by search queries, making use of facets, more-like-this and so on
