Project Overview

[VictoriaGuido]

Notes from the National Civic Day of Hacking Project - for updating in a readme or wiki somewhere if needed.

Looks for for the Rising for Justice Expungement Eligibility Guide in the docs folder.

The deterministic guide is deterministic.

High level story: A client comes in to RFJ and meets with a lawyer to review if they are eligible to have their records expunged. One client is a "case" and they may have multiple "charges" they're looking to get expunged. After completing the Eligibility Guide, the results should return one of three states -

1. Either the client is ineligible to get records expunged.
2. The client is eligible to get expunged.
3. The client MAY be eligible to get expunged.

For views

1. Top level data view
   1. information at the top of the decision tree - clients name evaluators name, data points on evaluator, charges in the case, outcomes of the case, date of the case.
   2. Could be in a table, flat view, whatever we decide from a design perspective.
2. Each case opens into a view for Deterministic workflow
3. For each charge indicator for eligible / ineligible
4. In the issues we’ve spec’d out a bunch of react components
5. A data model from which the views can be dynamically generated

User

• the pro bono attorney who’s meeting with the client

Current User Experience

• a piece of paper, has the documents from the case, prior to beginning to work with them and a determination guide.
• They go through the set of questions and scribble notes in the margins.
• based on the control flow in the guide, they come to a determination / recommendation with the client and then tell the client.
• If they make an error, it’s not controlled.

Goal User Experience

• Have them enter the information, record the info from the client, in a web form component, and code those responses into a document.
• If they come to a question like is this case more than 4 years ago - hits a radio button and that become data that’s recorded by the app.
• Print to pdf - may not happen today, but all the inputs would be recorded and put into a pdf document.
• PDF gets put on a USB and gets handed too Gwen.
• If it’s screen reading pdf all the better.
• If you get to the end of the guide, you could go on to
  • Another charge
  • Another case
  • Summary of recommendation
  • Print file
• Maximum at a glance feedback for attorney to see

In the future, could open this app up to the public, but we do have a disclaimer about how you should talk to the lawyer.

Two evaluation workflows

• could change if the law changes tomorrow
• Json will dynamically create workflows

Top Level functions

• Print to PDF
• Reset (you’re about to erase all the data you just entered, do you want to do that?)
• A card next to the table - right now you have not entered enough information to determine eligible. Based on this charge, this client is ineligible, do you want to continue? Once they’re determined eligible, it should indicate as such.

Deliberately preventing any retention of cases. The print to pdf feature is how it gets persisted to disc, because it’s PII, PMI every GDPR acronym.

The only way the data should be persisted is handing it to Gwen

In the guide

• at the top, if it’s actual innocence, that’s one type of motion
• 16803 - Interest of Justice, most complicated with a number of different waiting periods. If you have a recent case with a recent conviction, it makes you ineligible, or they’ll skip of it. If it’s in the 2-4 year window.

Implementation notes

• Review the issues in the repo
  • Include the top level data view, some of the nav buttons, the eligibility workflow, the at a glance indicator for rows, component-ry is on it’s way to being fully spaced out
• Features most important
  • Dynamic rendering - reading a json object and then rending them
  • Mapping components to a json object

Work issues

• validating the data model
  • needs to match the true workflow
• Are any of the data fields optional at any point? Yes

Split up issues and get to work

Using material UI.