Voting Systems

OK,

Finally finished it. Their happens to be a permission problem still though. Users not uid=1 will not be able to view the node that is recommended or access the recommendations page. Pretty sure you can fix that in the admin panel but havent done that yet. If any can shed some light on it please do. Here is where you can find the stuff: http://scottreynolds.us/Downloads/movielenssql.tar.gz

100k movielens is not done, it is in a different file format thereby requiring a different program.
Info from readme file:

The long-neglected VotingAPI documention is finally getting some attention. Those interested in reviewing the docs as they're written, helping with suggestions, or asking questions can check out the under-construction VotingAPI section of the Drupal Handbook:

• VotingAPI: A framework for voting and rating modules
• VotingAPI: The basics for developers
• VotingAPI: Full control for complex voting modules
• VotingAPI: Hooks for greater control
• VotingAPI: Data storage overview

I just came accross mediumvote (http://drupal.org/node/49767) which sounds amazing. Anyone tried using it yet?

-jd

 1st Call for Papers
 1st International Workshop on Computational Social Choice
 (COMSOC-2006)
 Amsterdam, 6-8 December 2006
 URL: http://www.illc.uva.nl/~ulle/COMSOC-2006/

MISSION

Computational social choice is a new discipline emerging at the
interface of social choice theory and computer science. It is

Right now, SimpleVote is the best example of how an external module can hook into VotingAPI's action functionality. I'm writing up more detailed docs on how it works internally, but for now let's take a quick tour. First, there's hook_votingapi_action_sets(), a hook that any module can implement to return a collection of 'action sets' for consideration whenever a vote result is processed.

Each action set includes some key information:

1. Meta-data, like name and description
2. Some behavioral data, like whether ALL of its conditions must be true or only ONE,
3. A set of 'condition' records that are evaluated
4. A set of 'actions' that are executed if the conditions are satisfied

Prior to the recent innovations with actions integration, the recipe for digg was to install vote_up_down and follow directions. Now, if you do that, you end up with function conflicts between voting api and voting_actions. I therefore removed voting_actions since it seems to be deprecated. Where do I go from there to get custom actions based on voting?

(note: I'm researching almost as I type and hope to be able to answer my own questions =)

Hello,

(I cross-posted this message to http://www.wechange.org/node/97 . I will be updating the remote version with link, corrections, etc, so see there for updates if your read this long after I posted it).

I would like to introduce you to a php voting API that I wish to develop further and for which I'd like to create a Drupal module. It is a complementary alternative or even replacement to the Drupal voting API.

Please, don't consider having a heart attack just yet. Please, read further and decide later.

Allow me to start from the beginning...

A world of alternative voting systems

It is a sad fact that for most people, whenever they think about voting or election, they can only think about what is known as "plurality voting", the voting method whereby you can only select one choice among many. Unfortunately, this voting method is demonstrably very bad.

One of the major VotingAPI improvements that's been in the pipeline for a while is an overhaul of integration with the Actions module. At present, the voting_actions module is used to set up specific vote results that will trigger things like promoting a node to the front page, or unpublishing it. There are some problems with the approach, though. First, there was no way for module authors to provide 'built-in' voting actions. Everything had to be set up by users. Second, there was no way to make decisions about action execution based on the content rather than the vote. In other words, polls need 10 votes to be promoted, but stories need 15. Third, there's really no reason that the functionality should be in a separate module -- actions integration should be exposed as an API for module writers, and should be tweakable by users who want more customization. It's a bit like the Views module philosophy: modules can expose default bviews, but users can make their own or override the defaults. To that end, the new VotingAPI actions system has been re-written. All the core code IS present, though the end-user UI for creating and overriding actions is still being written.