Closed JohnMwashuma closed 10 months ago
Thanks!
So the ballot form, I might suggest having two catergories/levels. Level 1 - Election Level Level 2 - Sub-Type
Presidential / General / Presidential / Runoff / HoR / General HoR / Women HoR / Component_Amazigh Senate / General Senate / Women
Thanks!
So the ballot form, I might suggest having two catergories/levels. Level 1 - Election Level Level 2 - Sub-Type
Presidential / General / Presidential / Runoff / HoR / General HoR / Women HoR / Component_Amazigh Senate / General Senate / Women
Cool so in total we have 3 columns on the ballots file. We add an extra column called sub_type
and rename the type
column to election_level
. So columns will be:
That said, will that then mean for the Election Levels that have the same name e.g. Presidential
will have unique ballot numbers?.
User story
Due to the need of the tally system to support dynamic ballot types, the current file structure that contains ballot types does not work well with this in mind. That said, a better file structure for ballot types and sub constituency ballots needs to be created so that it's a bit straight forward on how dynamic ballots will be added/removed during initial tally creation.
Proposed ballots file structure
This file will be used for creating all electrol races and ballots.
Example ballots file structure
Proposed Sub Constituency Ballots file structure
This is a separate file from the main sub constituency file. It's main purpose is to show the mapping/assignments of ballots to sub constituencies.
This approach will need good validation logic to validate that the sub constituency codes and ballot numbers are actually valid and do exist in the system. This also means we will do away with the ballot number columns in the main sub constituency file except for the number of ballots columns that is need to validate correct number of ballots have been assigned to a sub constituency.
Example Sub Constituency Ballots file structure
Related to:
https://github.com/onaio/tally-ho/issues/374