Stories that I voted on are still being recommended!!!

drupalina - December 10, 2008 - 03:16
Project:Content Recommendation Engine
Version:5.x-1.0
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:postponed (maintainer needs more info)
Description

In the Common Issues of the README file it says:
"CRE will never recommend a piece of content if that user has voted already on that piece of content."

But I'm looking through the recommendations (both in the page view and the blocks) and most of them I have already voted on.

I'm submitting this as a critical bug because this pretty much defies the whole purpose of *recommendations* -- i.e. recommending new content that I haven't already seen or voted.

BTW, I'm using Extra Voting Forms (depends on Voting API) module on a site powered by Drigg modules.

#1

Scott Reynolds - December 10, 2008 - 07:28
Priority:critical» normal
Status:active» postponed (maintainer needs more info)

As noted in the Readme the results can be one of two behaviors

1.) Display a list of up to max number of nodes (see admin/cre/node)of recommended content
OR
2.) List the top rated nodes

behavior number 2 occurs when:
1.) User has not voted yet
2.) User authored all nodes that have been voted on
3.) User has voted on every node in votingapi_vote table
otherwise, behavior number 1 occurs

ESSENTIALLY, behavior 2 occurs when behavior 1 fails to return any results

so the question is, have your user voted yet? Has the user authored all the nodes in the system? Has the user voted on every node in the votingapi table?

#2

drupalina - December 10, 2008 - 15:10

have your user voted yet?
My users have been voting since March 2008 ;) It's a sharing and voting site like Digg.com. I just installed CRE only today.

Has the user authored all the nodes in the system?
No, it's a sharing site, so _many_ users have authored nodes of Drigg content type.

Has the user voted on every node in the votingapi table?
You mean ALL the nodes within the system? Of course not. Some of the nodes he still didn't vote on and doesn't intend to.

So there are the answers.

Ultimately, the way that one would expect Content Recomentation Engine to behave, is to display all the nodes that that he still has the right to vote for. (the way that the system is set up is that only 1 (up or down) vote is allowed, and once it's cast, he can't vote on that node again).
So if I already voted on a particular node (it pretty much implies that I've already acquainted myself with it), what's the point of bring it up to my attention agan? People must always see new content that they haven't voted on yet. I think it's logical.

Thanks

 
 

Drupal is a registered trademark of Dries Buytaert.