@eventualbuddha and I made a number of changes to NH state ballot creation logic, all captured in some way or another on this branch.
Let's productionize/generalize the changes on that branch, and port them over to the VxDesign v3.1.0 release branch for November ballot creation.
There are also some scripts and notes that we added directly to the election-definitions repo here that belong on the VxDesign v3.1.0 release branch as well.
One thing that we didn't tackle this go around is using polling places as precinct names, to avoid the wonky looking "Town, Town, NH" strings in the app footers. This data is available on the NH SoS website. Let's see what else we can pull from that site that isn't available in the XML files. Another example that comes to mind is district names, which show up on final reports. We should cross-check NH SoS website data with the data that we're collecting from towns ourselves.
@eventualbuddha and I made a number of changes to NH state ballot creation logic, all captured in some way or another on this branch.
Let's productionize/generalize the changes on that branch, and port them over to the VxDesign v3.1.0 release branch for November ballot creation.
There are also some scripts and notes that we added directly to the
election-definitions
repo here that belong on the VxDesign v3.1.0 release branch as well.One thing that we didn't tackle this go around is using polling places as precinct names, to avoid the wonky looking "Town, Town, NH" strings in the app footers. This data is available on the NH SoS website. Let's see what else we can pull from that site that isn't available in the XML files. Another example that comes to mind is district names, which show up on final reports. We should cross-check NH SoS website data with the data that we're collecting from towns ourselves.
Once we complete all of the above, let's update the top-level checklist.