voting

(Submitted at five seconds of the deadline!)

<

blockquote>Abstract: I will introduce several features to enable communities of users to create and manage categories directly. Users will be able to vote to combine terms or to move terms under one another in a hierarchy.

Hi

Could anybody, please, tell if workflow module can be used for doing/checking things periodically and making a state transition basing on the check results?

Here's what I would like to be accomplished over the next month:

1. Fix all bugs currently in the issue queue and implement all feature requests.
2. Better display/theming of configuration options in the poll display (e.g. duration, starting date, eligibility, etc.).
3. Views integration.
4. Default options per content-type.
5. jQuery magic for ranking votes.
6. Email capability for electoral list - option to send to all who are eligible, those who have voted, or those who haven't voted.
7. Actual releases for 5.0 and 4.7 branches.

It's also time for some progress evaluation from last month, when I had the following priorities for my work on Advanced Poll:

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.

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.

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

-jd

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 =)