Voting Systems

Hi,

I've just released the user_karma module.

http://drupal.org/project/user_karma

I wrote this module mainly for Drigg. It started as a simple module (300 lines) to assign karma to a user every time s/he received a vote for his/her nodes or comments.

However, it has now matured into something much, much more interesting:

digg.com for ubuntu users? Maybe, but like the earlier version of digg; voting on just the nodes(just the voting). Zen theme in new pajamas! nodes have slideshow of imagefield pics(http://ubuntuwatch.com/node/12), with rip-off of the background buttons for multiple pics, from the lullabots! sorry :P sorry to moshe too ;-) (but you have it in new avatar now ;)

I don't plan to commercialize/earn-from-it in any way, if someone of you thought, it was part of my fun times, playing and implementing with Drupal. It was ready since the oct of '07 but could get it online in dec month. And after all Thanks http://HCoop.net/ !

(i know there are poor way of implementations, hacky job on vote button(half rip-off from rubybaboon), and peekaboo bugs are treating me good for IE.., etc..)

No, it's not based on drigg, project from scratch, but I recommend it to anyone who plans to begin with drupal building a similar website. I'll try to publish the recipe in the near future, if time allows... :)

After all hobby projects don't get your skills rusted, what do you say?
http://ubuntuwatch.com/

Hello people,

I've just finished developing Drigg 1.0.

http://drupal.org/project/drigg

The good news is that it uses the fantastic Voting APIs developed by Eaton (the manager of this group).

At the beginning, I had made the silly mistake of developing everything on my own -- thus developing the "simple_karma" module, where the only "simple" part was in its name...

Luckily, I realised what I had done, and spli the simple_karma module so that it would make a lot of sense and -- more importantly -- it would use the Voting API.

With the Drupal 6 code freeze, it's time to crack down on some of the existing VotingAPI bugs and put together the battle plan for something that's been a long time coming: VotingAPI 2.0, for Drupal 6.

What will VotingAPI 2.0 offer? Nothing that can't already be done with some elbow-grease. The goal is not to dramatically expand what it does, but to streamline the APIs and make things work a bit smoother.

Hi

I am currently using voting_api + vote_up_down on the smartphone apps site. I'd like to let the anonymous users vote, but in such a way that each user (for example, each IP address) can vote only once per node.

Can it be somehow done with voting_api?
If it can almost be done, I am not afraid of some PHP programing to finalize it, but I'd like to get some guidance on where to start.

Best regards,
Artem.

Hello,

I've just created a new karma module.
I am not entirely sure other people would be interested in it. It's well code, well commented, and it's about to be tested on a production server (http://www.freesoftwaremagazine.com).

Now... here is a (probably not comprehensive) list of features:

• Javascript voting; however, the module works 1000% even if the
  user doesn't have Javascript

• Abuse control. The module allows you to limit users on how many karma points
  they cna give, to a particular user or in general. The admin can also decide

Hi

I am thinking about tuning my vote_up_down based site into a bit more digg-like site. On Digg 50 votes per hour can outperform 500 votes per two weeks - it allows "hot" news to be pushed to the front page earlier. Can similar things be achieved with the help of voting_api?

1. I am thinking about attaching to every node, not only a "vote" counter, but also kind'a "internal priority" counter, that would be increased by user votes and decreased by time therefore making old votes less valuable.

It's been five weeks since the last update and a ton of progress has been made on Advanced Poll:

• Ported to Drupal 5.0 - all new development is occuring on the 5.0 branch
• Dynamically add or remove poll choices
• PostgreSQL support (additional testing needed)
• Start dates for polls
• Submit votes using Ajax
• List polls at /polls
• Cache voting results
• Add/remove individual users from Electoral List and a button to clear it entirely
• Allow votes to be reset
• Numerous bug fixes

Demo available at http://advpoll.ck37.com and additional discussion can go in the Advanced Poll working group. Please submit all bug reports and feature requests to the issue queue.

In the five weeks since the last update several features have been added to Advanced Poll module, and we are also working to improve usability and overall code quality.

New features include:

• Borda Count
• Electoral list tab
• View votes tab
• Cancellable votes

The module is undergoing rapid development so bug reports and feature requests are much appreciated.

There's now a branched CVS version of VotingAPI for Drupal 5. Module developers interested in getting a head start on porting their voting modules can begin using it now -- it's fully functional, though for now Views integration has been pulled out. In addition, the Actions integration is now in a separate module that's still bundled. I'm working (again) on the UI for it and that should be coming within the next few weeks if all goes well.

A number of serious technical hurdles have always made VotingAPI/Views integration wonky: maintaining the .inc file as it currently stands would only increase confusion. I'm working on a better solution, as well as a potential patch for Views module if necessary. Once it's in place, I'll add votingapi_views.module to the DRUPAL-5 branch.

The Advanced Poll module now supports approval voting in CVS. Approval voting is implemented by adding a "maximum choices" option for each poll. If it is set to one the poll behaves as usual and users can only vote for one option. If it is set to something else (something greater than one, or 0 for no limit) users may check off the choices that they approve of, up to whatever "maximum choices" is set to. For example, if maximum choices is set to "2" users may vote for their top two choices in a given poll.

About Advanced Poll

What?

A few days ago, I compiled a list of all the node review modules I could find at the time, and wrote up an article comparing them: http://www.lullabot.com/articles/a_review_of_node_review_modules. The amount of overlap in these modules is, quite frankly, stunning. Yet they all do slightly different things. Node Review handles multiple axes. Simple Vote merely stores the aggregate score for a node. User Review allows you to place a comment with your vote. Vote Up/Down handles a simple "yes/no" style of voting.

It occurred to me that if we took a step back, we might be able to develop "one voting module to rule them all." Rather than having to keep implementing these new voting modules because others "almost" do what we want but not quite.

I've looked briefly at customvote.module, which looks as though it endeavors to be that tool. But I'm thinking something slightly different: a voting API field for CCK.

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.