The current voting method, while good, is not the preferred ballot for modern
voting algorithms. A better method would be a ranked ballot, allowing the user
to rank existing solutions into a list of preferences. This would allow the
system to use theoretically sounds voting algorithms for the calculation of the
best solution, and vastly increase the capability for users to express their
preferences.
This would require some modification to the pirate_consensus module, as well as
a new UI interface to allow for ranked voting. It would be best for this
interface to be dynamic AJAX/Javascript as to improve the experience of the
user.
The consensus_model can be updated with a rank model field, allowing it to
reference the rank of the solution. The Consensus model should remain unaware
of the other Consensus models at the same depth in the tree, the validity of
the ranking must be enforced at the interface level.
Original issue reported on code.google.com by fragro on 10 Feb 2011 at 11:14
Original issue reported on code.google.com by
fragro
on 10 Feb 2011 at 11:14