votingworks / vxsuite

https://voting.works
30 stars 5 forks source link

precinct-scanner: handle scanned ballots when setting precinct #1009

Closed carolinemodic closed 10 months ago

carolinemodic commented 2 years ago

Changing the precinct that the precinct-scanner is configured for doesn't reset the ballot data, so you can scan ballots for precinct-1 and then configure the scanner for precinct-2 and there are still precinct-1 ballots in the data.

eventualbuddha commented 2 years ago

What should this do? Should we require the polls be closed when changing the precinct? That the ballot data be zeroed out?

benadida commented 2 years ago

I believe this should delete scanned ballot data but with a warning first.

cc @mcchilders thoughts?

mcchilders commented 2 years ago

What is the reasoning behind this question, I think I'm missing context? Here are a few scenarios where you'd want the same precinct scanner to have diff configs during the same election:

Deleting ballot data is v dicey, and there are good reasons to never do it until the election is fully over, so I would lean towards retaining all ballot data, even when you switch the config on a machine, and then having checks in Election Manager that flag when you're uploading entirely/partially duplicate CVRs within a CVR file (e.g. Scenario 2 above, when you've exported CVRs at the end of e-day and loaded those, but then also exported a cumulative CVR file again after scanning absentee ballots that has both).

adghayes commented 10 months ago

We opted, back in the polls suspension project, to not allow precinct changes after ballots have been scanned. If absolutely necessary, the machine will need to be backed up and reconfigured.