The audittools from pbstark

audittools's People

Contributors

Stargazers

Watchers

audittools's Issues

replace sorted ballot-to-look-up textarea with list + user input

For each contest, enumerate the candidates and allow the user to select which candidate(s) received votes on that ballot.

In vote-for-one contests, this should be drop-down select, with an option for "none" and "overvote".

In vote-for-k, tic boxes with option for "none" and "overvote," and logic to test that no more than k are selected (throw some alert/color signal if so)

The current <textarea> for the sorted lookup table should be replaced by a

containing an

would have
sorted_number, ballot, batch_label, which_ballot_in_batch
none overvote Candidate_1_name etc.
Use jQuery to construct an .change() method for each of these selects that increments the audit tally for the candidate selected (or decrements it, as appropriate, if it changes). A tentative strategy for implementing this is to have a hidden clone of each select, with a related id, so it's easy to compare the previous state to the changed state.

$(".ballot_432").change(function() {
find previous selected candidate for that ballot using $(".ballot_432_clone").val()
decrement spinner count of that candidate if not {none | overvote}
increment spinner count for new selected candidate, $(".ballot_432").val()
select new candidate on cloned copy $(".ballot_432_clone").val($(".ballot_432").val());
}
)

create json structure with contest and audit parameters

Button click will construct a json structure for the audit and do something to report that structure

For each contest:

the reported results are in a structure:
1. contest name, total ballots, "vote-for-k"
2. for each candidate:
  1. candidate name
  2. reported ballots
audit results are in a structure
1. seed
2. #ballots audited
3. for each audited ballot
  1. candidate(s) the audit found on the ballot (or "none" or "overvote")