RE: [development] Rating module quality
Not having looked at the voting api... is it merely a rating module or does it have the ability to have the users comments with their vote? Also, assuming that these votes are tied to a user account, do these votes/comments reflect account status? Example, Bob really likes module B and creates several accounts to mess with the results, bob's accounts are blocked... does this reflect into the count? Also, we have more spammers now (not a lot but...) when we block there account can we also delete the comments in the vote (shows up in tracker)? It would definitly be a vector for spam. Download.com has this issue at times with their user supplied review/votes... -sp ________________________________ From: development-bounces@drupal.org on behalf of Khalid B Sent: Thu 1/26/2006 9:31 AM To: development@drupal.org Subject: Re: [development] Rating module quality I think there is value in both voting and # of downloads. They balance each other and compliment each other so well. If a module is downloaded a lot, but gets a poor rating, it will eventually get less downloads. The number of votes is also important, a module rated 10/10 by 2 people is questionable when compared to a module that got 7/10 from 120 people. So, let us go ahead with both of them.
VotingAPI is a pure storage/calculation system. At present there are a couple of small modules built on it, and a couple of large-ish ones under development. Modules use the votingapi_set_vote() function to cast a vote for a user, and similar retrieval functions. the votingapi_hook has a 'calculate' $op that allows modules to do custom filtering of votes before aggregates are calculated -- filtering out banned users, etc. There are a couple of example implementations (latestgreatest.module and simplevote.module) that use it, as well as a couple of larger projects. I'm in the final stages of converting nmoderation.module to the API as well. To accomplish what you're talking about, we might: 1) Turn comments on for projects 2) Alter the comment form on project nodes to add a multicriteria ratings widget (A series of form radio buttons, 1-5, for each criteria) 3) Persist the votes using the votingAPI 4) Calculate the averages (filtering out votes from banned/blocked users) 5) Alter node_view for project nodes to put the average/median/whatever votes into the project node body. 6) Alter comment_views for project nodes to put a particular user's ratings for a module next to any comments about the module. That approach would be relatively straightforward and wouldn't require a lot of hacking. The only drawback I can think of is that it would append the user's rating of the module onto EVERY comment they post. --Jeff -----Original Message----- From: Steven Peck [mailto:speck@blkmtn.org] Sent: Thursday, January 26, 2006 12:44 PM To: development@drupal.org; kb@2bits.com Subject: RE: [development] Rating module quality Not having looked at the voting api... is it merely a rating module or does it have the ability to have the users comments with their vote? Also, assuming that these votes are tied to a user account, do these votes/comments reflect account status? Example, Bob really likes module B and creates several accounts to mess with the results, bob's accounts are blocked... does this reflect into the count? Also, we have more spammers now (not a lot but...) when we block there account can we also delete the comments in the vote (shows up in tracker)? It would definitly be a vector for spam. Download.com has this issue at times with their user supplied review/votes... -sp
participants (2)
-
Jeff Eaton -
Steven Peck