search

votingworks / vxsuite

https://voting.works
GNU General Public License v3.0
30 stars 6 forks source link

Support different candidate orders across ballot styles #5074

Open arsalansufi opened 4 months ago

arsalansufi commented 4 months ago

https://votingworks.slack.com/archives/C06H2PBP0MU/p1721331994723829?thread_ts=1721331364.873059&cid=C06H2PBP0MU

We may support bits and pieces of this, but let's audit the system across HMPBs/VxScan and VxMark and make sure that we actually support this everywhere.

arsalansufi commented 1 month ago

Copying from Slack

@kevin: @roe and I just synced on https://github.com/votingworks/vxsuite/issues/5074 (the question of different candidate orders per ballot style) and reached a few conclusions:

  • Contests have one top-level definition in each election definition.
  • Contest order is defined for HMPBs via per-ballot-style grid layouts.
  • VxMark almost certainly just uses the order in the top-level definition, not the order reflected in grid layouts (which isn't even the best way to represent order on a VxMark).
  • This means that we can support different candidate orders per ballot style for HMPBs but not on VxMark.
  • Supporting this on VxMark would be a big change and risky to try to tackle right now.
  • This ultimately isn't required for cert. Cert mentions supporting candidate rotation, but doesn't mention candidate rotation on a per-ballot-style basis.
  • We don't need per ballot-style candidate rotation on VxMark for NH any time soon (maybe ever).
  • So consensus is that this will be a v4.1 feature addition.