Known bugs or issues:
-- randomize each voting list
-
- it'd be nice if the ordering were persistent, so I could drag
the candidates around, then come back later (loading the page anew),
make tweaks, and submit.
if it were aware that it's a five-seat election and could say
explicitly who the whole board is.
-- it's probably a good thing that users can't check out what alternate
- voting systems would have done at the click of a button. =)
- (though of course they could work it out themselves.)
-
- is there rhyme or reason to the ordering within each row of the
second table in pref_tables? it could be, eg, sorted by magnitude
of victory, narrowest first.
helpful for auditing, too, as one could separately match names to the
correct list and match addresses to names.)
-- just a tiny suggestion - possibly it could be a good idea to add a
- counter/line-count to the table with keys and vote results so in one
- glance someone can see that the number of votes matches the number of
- voters.
-
QuickVotes
==============
add_index "elections", ["user_id"], :name => "fk_user_election"
create_table "pictures", :force => true do |t|
- t.column "filename", :string
- t.column "content_type", :string
- t.column "size", :integer
- t.column "width", :integer
- t.column "height", :integer
- t.column "parent_id", :integer
- t.column "thumbnail", :string
- t.column "created_at", :datetime
+ t.column "filename", :string, :limit => 200
+ t.column "data", :binary
+ t.column "filetype", :string, :limit => 100
t.column "candidate_id", :integer
end
+ add_index "pictures", ["candidate_id"], :name => "fk_candidate_picture"
+
create_table "rankings", :force => true do |t|
t.column "vote_id", :integer
t.column "candidate_id", :integer