You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When implementing parsing hart cvrs for the batch inventory tool, we realized that in the sample cvrs we were using the contests for the democrat and republican versions of contest had identical contest names in the cvr files coming from hart. The contest ids, as expected, are unique between democrat and republican. If this is how all hart cvrs look for primary elections this could present a problem when parsing cvrs for ballot comparison audits, and in the batch inventory tool. We may need to require the contest name in the "target contests" include the party name that is passed through as in the xml for each primary cvr xml file.
When implementing parsing hart cvrs for the batch inventory tool, we realized that in the sample cvrs we were using the contests for the democrat and republican versions of contest had identical contest names in the cvr files coming from hart. The contest ids, as expected, are unique between democrat and republican. If this is how all hart cvrs look for primary elections this could present a problem when parsing cvrs for ballot comparison audits, and in the batch inventory tool. We may need to require the contest name in the "target contests" include the party name that is passed through as in the xml for each primary cvr xml file.
See this thread for sample files and discussion. Note that the sample files are from a mock election, its possible this issue is a configuration error in the mock election and not relevant in general: https://votingworks.slack.com/archives/C013V6CT9H9/p1724676881810049
The text was updated successfully, but these errors were encountered: