Use Case: UC06.06.05 / View PVRDR/Jury Wheel Extract
Use Case: UC06.06.05 / View PVRDR/Jury Wheel Extract
Attribute / Details /System Requirements: / S26.1 VoteCal must allow authorized SOS administrators and authorized county users to input, track and review Public Voter Registration Data Requests (PVRDRs), including:
§ Requestor name;
§ Requestor ID number and type;
§ Requestor organization;
§ Requestor residence and business addresses;
§ Requestor contact information (phone, fax, email addresses);
§ If Requestor is acting as an authorized agent for a qualified party, the name, address and contact information for the party legally qualified to purchase the data;
§ Requestor’s stated purpose/use for the data;
§ Date of application;
§ Date application received;
§ Basis for qualification (election, party, academic, journalist, etc.);
§ Date of application fulfillment or denial;
§ Status of application;
§ Criteria used to select/exclude records for the extract; and
§ Filename(s) and number of records provided in the extract.
Description: / The purpose of this use case is to allow a user the capability to view previously generated extracts for Public Voter Registration Data Requests (PVRDR’s) and Jury Wheels. (Jury Wheel Extracts are a subset of PVRDRs, differing primarily on the formula for extracting voter records.)
Actors: / SOS User, County User
Trigger: / User initiates the use case when a PVRDR or Jury Wheel Extract has been generated and the user would like to view the extract.
System: / VoteCal Application
Preconditions: / § A PVRDR or Jury Wheel extract request (a PVRDR record) has been entered into VoteCal, and the extract has been generated.
§ All global preconditions apply.
Post conditions: / § A PVRDR record storing the pertinent information from the PVRDR request will be created or updated. The PVRDR record will be associated to the requesting Organization.
§ Organization Transaction History records will be created as needed, storing the information about the PVRDR being entered, the entry date, status, etc.
§ If a PVRDR extract was generated, then the files will be available for downloading and eventual dissemination.
§ All global post conditions apply.
Normal Flow: / 1. View PVRDR/Jury Wheel Extract:Users can check the PVRDR to see if the extract has been generated. When the PVRDR has a status of “Completed”, then the extract was successfully completed and is ready for download.
2. User accesses the Organizations Management section of the system. User drills down to the specific PVRDR to download extract files from, following the general flow outlined in Steps 16 to 19.
3. System presents the UI06.xxx Enter PVRDR/Jury Wheel Extract Request screen.
4. User goes to the “Extract Details” section of the screen.
5. System shows links to the files generated for the PVRDR extract.
6. User clicks on the links and downloads the generated PVRDR file extracts. The files can then be disseminated as necessary (e.g. CD ROM, e-mail, etc.).
7. System creates Organization Transaction History record storing that information about the extract file being downloaded, and the user that performed the action.
Alternative Flows: / N/A
Exceptions: / N/A
Includes: / N/A
Frequency of Use: / TBD. PVRDR requests are expected to occur more frequently during election years. Jury Wheel Extract requests come in once a year for each court.
Business Rules: / N/A
Assumptions: / N/A
Notes and Issues: / § The generation of a PVRDR file extract is described by UC06.07.01 Generate PVRDR File Set.
§ Per SOS, the generated PVRDR extract files are password-protected before being disseminated.
Revision History
Date / DocumentVersion / Document Revision
Description / Revision Author
04/06/2010 / 0.1 / Initial Draft / 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}
04/06/2010
Version: 0.1 / Page 1