Jonathan E Hogue
Jonathan E Hogue
Should at least be sorted by highest score, right? 315 should have a negative score, and 1466 is positive. You'd expect 1466 to be first?
But would also make sense to remove negative scores from recommended_(). maybe expose that through a new method not_recommended_ or something.
recommendable:users:134255:recommended_courses value score 315 -1 1466 1
I'm not sure what you mean by ratings, exactly. Checking redis, it seems like the data is consistent with what I'd expect from the steps I followed in the first...
So, my course class has a rated? method, unrelated to recommendable. Wonder if that's causing a problem.
Rename that method and reran everything. Same result. I guess next step is to create a minimal example app and try to reproduce the problem there.
I've created a simple sample app, but noticed something that is probably the culprit. Notice, that we look for (5,3,4) but we get back [3,4,5]. This is rails 3. Not...
I do something like this to deal with this same situation from solr. Not the most efficient, but database agnostic. If I could access the raw scores, I could do...
> So while that list does contain the best recommendations > Except that 4 should not show up at all since it was disliked. At most, it should show up...