/ VoteCal Statewide Voter Registration System Project
Use Case: UC05.18.01 / Determine Organization that Requested PVRDR using Salt Record

Use Case: UC05.18.01 / Determine Organization that Requested PVRDR using Salt Record

Attribute / Details
System Requirements: / S26.8 VoteCal must provide the ability to record the salted record(s) associated with each PVRDR.
S26.7 VoteCal must include the ability for authorized SOS administrators to insert one or more fictional registration records into each PVRDR extract to “salt” the data extract so that improper use of the data can be traced to the particular PVRDR data release.
Description: / The purpose of this use case is to determines to which individual or organization requested a particular PVRDR extract was provided by using information from a salt record. This may be useful to identify and prosecute organizations which may be abusing the PVRDR listviolated law by misusing confidential voter registration data.
Actors: / SOS User
Trigger: / User initiates the use case whenever there is a need to determine which organization requested a particular PVRDR, e.g., during an investigation into improper use of PVRDR data.
System: / VoteCal Application
Preconditions: /
  • All global preconditions apply.

Post conditions: /
  • If the Salt Record was found, then the user will get information about the PVRDR request, including the requesting Organization.
  • All global post conditions apply.

Normal Flow: /
  1. User initiates the organizations management function from the system.
  2. User selects “Look up Organization that requested a PVRDR by Salt Record”.
  3. System presents the UI05.xxx Look up PVRDR by Salt Record screen.
  4. User enters information from the Salt Record, including:
  • Name
  • Address, City, State, Zip Code
  • Phone Number
  • Comments
  • Date of Birth
  • Gender
  • Political Party
  • Precinct Assignment
  • Voter Participation History
The more specific the information the user provides, the more accurate the search results will be. Ideally, the user should have enough information that uniquely identifies the salt record.
  1. User selects the “Query” command to initiate the PVRDR search.
  2. System queries for Salt Records matching the criteria specified by the user. The results are matched up with the associated Salt Record Assignments, PVRDR Extracts, PVRDR requests, and the requesting Organizations.
  3. System presents the query results in a list, displaying the following information:
  • Organization Name
  • PVRDR Request Date
  • PVRDR Extract Date
  • Summary information about the Salt Record (Name, Address, etc.)
  1. User views Organization and PVRDR details
  2. User selects the “View Details” command for an item in the list of search results.
  3. System queries the appropriate Organization, PVRDR, and PVRDR Extract records and displays the following information:[BMc1][cik2]
  4. Organization Name (this will be a hyperlink to the organization’s UI06.XX Organization Details screen)
  5. Address, City, State, Zip Code
  6. Phone Number
  7. Contact Name
  8. PVRDR Request Date
  9. PVRDR Criteria
  10. PVRDR Extract Date
  11. Salt Record Name
  12. Salt Record Address, City, State, Zip, etc.
  13. Salt Record Phone
  14. Salt Record Comments
  15. Salt Record Date of Birth
  16. Salt Record Gender
  17. Salt Record Political Party
  18. Salt Record Precinct Assignment
  19. Salt Record Voter Participation History

Alternative Flows: / 7a No data matching the entered Salt Record was found
7a.1 System presents message stating that the entered Salt Record information could not be matched with any PVRDR requests.
7a.2 Go back to Step 3
Exceptions: / N/A
Includes: / N/A
Frequency of Use: / This will occur at the discretion of the Investigations unit depending on how often an organization is suspected to be misusing the PVRDR list.
Business Rules: / N/A
Assumptions: /
  • Salt Records can be only associated with one PVRDR extract.

Notes and Issues: / N/A

Revision History

Date / Document
Version / Document Revision
Description / Revision Author
12/15/2009 / 0.1 / Initial Draft / Victor Vergara
01/20/2010 / 0.2 / Document Revisions / Victor Vergara
01/20/2010 / 1.0 / Minor edits and release to client. / Maureen Lyon
02/04/2010 / 1.1 / Incorporate Client Feedback / Victor Vergara
02/04/2010 / 1.2 / Submit to client for review / Maureen Lyon
03/17/2010 / 1.3 / Incorporate Client Feedback from QA Checklist / Kimanh Nguyen
03/19/2010 / 1.4 / QA and Release to Client for Review / Don Westfall
04/06/2010 / 1.5 / Update with client feedback / Kimanh Nguyen
mm/dd/yyyy / 2.0 / Submit to Client for Review (Deliverable 2.3 Draft) / {Name}
mm/dd/yyyy / 2.1 / Incorporate Client Feedback / {Name}
mm/dd/yyyy / 2.2 / Submit to Client for Approval (Deliverable 2.3 Final) / {Name}
03/1904/06/2010
Version: 1.54 / Page 1

[BMc1]Why would we not just display (or make available for display) all detail from the Salt Record, the PVRDR record and the Organization record?

KN: Added additional data fields. Should there be any more?

[cik2]1Agree

KN: See above.