The
count method is allowed to change after set-for-election. Filter set
should not though. Neither should be Id or Region. Whit, please take
a look at those. Its 10 minutes to fix.
Changing the count method does not reset any
existing counter batches by design. You can count some ballots
for a vote center using memory cards and then count some more using
central count or manual entry.
The Vote Center Editor, however, is not in
good shape. We are aware of the problems, but the truth is they have never
crept very far up the priority queue since no real-world problems situations
have come up, and this is the first report from anyone. I'll list some of
them off here for the record so people know to avoid them:
Hmmm, now that I see this list, I think we'll just
disable changing the number of memory cards or count method after
set-for-election for now. Whit, get those too please. The reason
these never come up is that no one touches the vote center editor after
set-for-election. Preventing users from doing this won't fix the
oddities for before set-for-election though. I'll re-write the Vote Center
Editor when I get a chance. Sorry about these folks; "I didn't write
the first one" is my only excuse.
There
are two kinds of manual entry. One kind we can call "Pure
Manual Entry", where a new counter batch is created explicitly for the purpose
of receiving manual entered results. An example of this is Alaska.
You use the "Manual Entry Only" count method for this type.
The second kind of manual entry is called "Manual
Modification". With this type, users can modify existing counter
batches. For example central count decks after they have been fed, or
memory cards after they have been uploaded.
What
you did was try and do a manual modification of a central count vote center that
has no decks yet comitted. This meant there was no counter batches to do
manual entry on. Similarly, the default vote centers each have no report
precincts. Manual modification is done on report precincts, so again there
was nothing to modify. The error message was written for a third similar
case: where there are no counter batches in the region of the logged in
user. I'll change the error message to read "No Counters Available to
Modify" to be generic to all cases.
Ken
|