Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VR content can vary by election date (is election specific) #3

Open
carl3 opened this issue Aug 31, 2017 · 1 comment
Open

VR content can vary by election date (is election specific) #3

carl3 opened this issue Aug 31, 2017 · 1 comment

Comments

@carl3
Copy link

carl3 commented Aug 31, 2017

Organization Name: Carl Hage

Organization Type: 4

Document: VoterRecordsInterchange

Reference: 3.1.6.18 The VoterRegistration Element

Comment: There may be 2 pending elections (e.g. LA has one in October & November),
and the second election might require a new precinct split, e.g. for a proposed district formation
or transfer. The precinct assignment for the first election might be different than for the second.

During redistricting, the district assignments may change. A current and upcoming election might
have different congressional districts, for example.

A voter might move after registration closes for one election but before closing for a subsequent
election. The voter would go to the poll location for the former address in election 1 and poll
location for newly registered address for election 2.

Poll locations, precinct consolidation, and mail-ballot precinct status vary by election date. There
can be 2 upcoming elections within the election cycle where poll locations are required to be final.

Suggested Change: Add an <ElectionDate> element to <VoterRegistration>
in a retrieval request to select a particular election, and to qualify the effective date for data
returned in a response. (The response might give the effective election date to qualify the
response even if no specific date was selected.)

Alternative: Allow data for multiple upcoming elections or to distinguish election-specific content
by creating an <ElectionDate> element with multiple instances allowed to contain response
data qualified by each active upcoming (or past) election. (Using a single selected or reporting
date seems simpler.)

Note, it can be useful to report the scheduled future election dates for a voter, along with the list of districts.

@JDziurlaj
Copy link
Collaborator

Because we do not currently implement a records retrieval capability, the alternative change would be more feasible. However, I would be interested in seeing if VIP provides such functionality, and how it is implemented. I also worry that this may make implementation more difficult.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants