votingapi

One thing that's been on my mind ever since the inception of the Design Initiative is some form of reputation system for design.drupal.org. If we can make this fly I'd be hugely in favor of it, and to that end I've put together a basic model of what this could look like (including an implementation), I'll get to that shortly, first I want to look briefly at what exists in Drupal ecosystem already - well, at least what I know of.

Lists of people who do stuff

Hi -
So far I've implemented the advanced rating recipe with fivestar + votingapi + nodecomments. So far, I"ve been able to create a 'Store' object and configure cck, nodecomments & fivestar so a 'Review' object can be submitted and displayed after the main node content.

The 'Store' object has fivestar enabled and the 'Review' object has the fivestar widget as a cck field. So far so good.

Now, what I want to do (and this is where I'm running into problems) is to create a table view that will display the following fields:

Store name
Average rating 5star widget

I am looking for a way to create a view of the the most recently voted upon posts. Any ideas how?

A view export would be nice!

Thanks in advance

We have finally gone live with our redesign of the Georgia Podcast Network! For a rundown of what's new from an end user standpoint, check out our announcement blog post.

GAPN is based on Drupal 5.7, and makes heavy use of the following modules: CCK, Views, Workflow-ng, FeedAPI, ImageCache, Usernode, Bio, Fivestar, and Voting API. That's not a full list, but the site leans on those the most.

Additionally, we built a custom theme and wrote several custom modules to get things working just the way we wanted them to. In writing these modules, we built custom Drupal integration for getID3, SWFUpload, and the JW Media Player.

Hope you like the site! I'll be happy to answer any "how did you do that?" questions if you have them.

I just uploaded a stand-alone module that provides Services methods for the Voting API. This allows external applications to access and modify Voting API data for Drupal objects. For example, a Flash application could implement an interface for voting on nodes.

I've submitted this as a feature request to the Voting API project at:
http://drupal.org/node/241453

If you use the Voting API and Services, please help me test this and support its inclusion in future Voting API releases. Let me know if you have any questions or suggestions.

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

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