We need to inform the user if their browser is not supported (e.g. IE6) to make sure that they know the application will not work with their version of their browser. To do this, we need to:

1. Add code to warn user for unsupported browser.

We need a way to see user behavior in websites

We want to conduct measurement of the impact associated with this software. One of the tasks is to instrument the webpage to add standard and custom metrics.

Signup for Google Analytics (and associated Google Accounts)
Setup Google Analytics code
Design appropriate metrics
Implement metrics

The form filling proof-of-concept is currently limited to a form that is single page. We need to enable form-filling for multiple-page forms. These forms must look correct when printed on US letter paper size.

As part of the project's approach on form filling by overlaying text on form images, we need to identify the location (in x, y pixel coordinates) where individual field will need to be filled in the form. We need to create detail step-by-step instructions to allow other volunteers to do this.

Tasks are as follows:

1. Identify and document (in README.MD) procedures for Mac on how to identify the (x,y) pixel offset using Preview (dragging selection rectangle).
2. Identify and document (in README.MD) procedures for PC on how to identify the (x,y) pixel offset using paint.
3. Identify and document (in README.MD) procedures for Linux on how to identify the (x,y) pixel offset using the default drawing app.

As the number of volunteers and external services / accounts increase. The project needs a way to manage accounts, credentials and secrets (e.g. API keys).

Research and recommend a team wide accounts / password / credentials / secrets management system.

We need to understand and document how to determine the lowest browser setting
Related to #41 .

1. Identify how one can emulate specific versions of browser for testing.
2. Document procedures to emulate and check browser for compatibility.
3. Identify which Browser (IE, Firefox, Chrome, Safari, etc) we are supporting.
4. Identify which version the software supports.

We want to have a “live” Beta page that will allow us to test the software as-deployed in the cloud instead of in local laptops. This will allow users to interact and test with the Beta version whilst keeping the main.

Setup Beta branch
Setup Beta branch related GitHub Actions
Write documentation on code promotion procedures

This project has volunteers that uses a number of different OSs.

With certain OSes (e.g. Windows, old LTR of CentOS, etc) will encounter severe friction when new volunteers are attempting to set up the development environment.

We should investigate and document steps (especially for Windows) on how to use dockerized development environment to expedite setting up of development environments.

We need to make sure our instructions covers how a user can run test (e.g. npm test) within the docker container and access the local server that serves the static pages.

We should aim to make dev environment setup as pain free as possible for hackathon scenarios.

We have a docker hub organization account that can be used: https://hub.docker.com/orgs/openseattle

We need to add a favicon to the web UI to replace the default "React" favicon.

A large version of the logo can be found in:
https://democracylab-marlok.s3.amazonaws.com/thumbnails%2Fmark%40democracylab.org%2FnewFile.jpeg_1571933640.2174747.jpeg

Ref: https://en.wikipedia.org/wiki/Favicon

Use an .nvmrc file as the source of truth for node version used in this project

As of July 2019, RCW 9.96.060 Section 5 was amended so that all marijuana misdemeanors can be vacated, see: https://apps.leg.wa.gov/RCW/default.aspx?cite=9.96.060

Every person convicted of a misdemeanor marijuana offense, who was twenty-one years of age or older at the time of the offense, may apply to the sentencing court for a vacation of the applicant's record of conviction for the offense.

These also have a separate form.

This means the current logic and crime classification needs to be updated. Marijuana misdemeanors are a special case and need to be handled as such in the logic. This entails:

1. Adding a new crime classification
2. Modifying the eligibility logic to handle this case

I'm going to take a first pass at a fix this week.

For some reason gh-pages is failing to deploy properly when using the GitHub actions workflow but correctly deploys using npm run deploy.

I think this is being caused by the git history being purged each time it runs as simply running npm run deploy adds a commit instead of removing the entire history. For now, website deployments will be manual after a series of commits / PRs.

https://hub.docker.com/orgs/openseattle

Helps with code quality, examples:

https://github.com/airbnb/javascript
https://airbnb.io/javascript/react/

The form-filling module's proof-of-concept is limited to a single legal form, we'll need to expand it such that it can auto-fill multiple forms.

Convictions related to DUI has a longer exclusion period. However, the current calculator logic does not account for this.

Currently for "(yearsSinceLastConvictionDate >= 5)" in Elgibilitytimelinecalc

("The latest conviction date (" + lastConvictionDateString + ") is within the last 10 years.");

Should be ("The latest conviction date (" + lastConvictionDateString + ") is within the last 5 years.");

Originally:

Then we click the first "X", and the result is:

Is that to be expected?

The user is expected to be able to leave inputs "empty" or undefined. The calculator logic needs to be able to handle them gracefully (best-effort calculation).

The current auto-form-filling proof of concept uses raw html / css / js to achieve its objective. However, the rest of the application uses React components. We would like to refactor the form filling feature to use react component to facilitate future integration with the main app.

Description:
When testing the master branch I tried the entire process with a squashed window and the results form has the same behavior as before #13 where the table doesn't retain useful context as to which text belongs to which columns.

Expected Behavior:
The results form should have the same behavior as the entry form where when the table is squashed, the column names follow the text.

System and Software:

• Browser: multiple
• Exact URL: no route switch

Additional context
n/a

We could research the feasibility of automating the e-filing of completed paperwork in various jurisdictions, beginning with King County (https://www.kingcounty.gov/courts/clerk/documents/file.aspx).

Name and DOB are the two overall form inputs and because of the difference in input they have different heights. Simply force them to be the same height.

We need to write tests, and testing infrastructure is required to do so. We need to decide on the testing framework and add it to the codebase.

Explore the feasibility of automating queries of the WA Case Search website (https://dw.courts.wa.gov/index.cfm?fa=home.home) to help attorneys and/or individuals populate their criminal history as accurately as possible.

As part of the project approach to form-filling via overlaying text on images of forms, we'll need to generate "definition" files for each page of each from in order to record information necessary to enable population of form fields in the correct coordinates.

We currently have a crude Proof-of-Concept (POC) Google Sheet implementation in
https://docs.google.com/spreadsheets/d/1DC43NRW4N-8RUXqnfn3K72SKu4vo7yhtrppgAgAXYAA/edit#gid=0

Tasks:

1. Investigate and confirm current Proof-of-Concept approach to form definition.
2. Update existing Proof-of-Concept to comply with confirmed definition schema.
3. Create instructions (in README.md) in the use of the definition generation tool.

We need to communicate the build version to our users in the frontend in order to help with debugging.

We'll need to make sure maintainers can identify version numbers against deployments

We have a staging deployment "maps to Beta branch" that deploys beta code to pre-production.
We need this "beta" page clearly communicate that it is a beta version.

We need specific examples of test "clients" with convictions input and corresponding (verified) vacation outputs.

We need to create a proof-of-concept for automated form filling.

We have chosen to use image overlay-with-text as the approach for this POC.

The following google sheet is used to facilitate identification of form filling elements.
https://docs.google.com/spreadsheets/d/1DC43NRW4N-8RUXqnfn3K72SKu4vo7yhtrppgAgAXYAA/edit#gid=0

Explore the feasibility of automating the population of the forms required to submit a conviction vacation request. The required forms can be found at https://civilsurvival.org/new-hope-act-forms/.

The project currently has a proof of concept automated form-filling module. However this module is not integrated with the main application.

We need to preemptively design the proper interface with the main module for integration in the very near future. We'll need to be able to auto fill forms of different combinations of conviction types in "one-shot".

Part of the design includes the consideration of:

• How do we model the fields in a form-page?
• How do we model multiple pages in a form?
• How do we translate upstream input values into these form elements?

hello Stephen Chan, In the project "Multi-objective Genetic Algorithm Optimization of Water Supply Systems " the files:

EPANETInputLocation = "c:\EPATEST\robmanualnetwork.inp";
pipeDatabaseInputLocation = "c:\EPATEST\robtestpipedatabase.txt";

Could you provide us with the structure of those files? Thank you for your great contribution.

Our approach to automatic form-filling is to use text overlay on images of forms. We need to extract (from word, pdf, etc) the legal form into images with specific Pixel Per Inch (PPI).

The task is as follows:

1. Adopt a consistent naming convention for form images.
2. Extract form images at the requisite 200 Pixel Per Inch.
3. Name the forms according to the naming convention.

The forms are as follows:

Forms to generate -

• Motion and Declaration for Order Vacating Conviction
• Notice of Hearing
• Order on Motion Re: Vacating Conviction

[Extra for felonies]

• Motion and Declaration for Order Vacating Record of Felony Conviction (MTAF)
• Order on Motion Re: Vacating Record of Felony Conviction

[For Marijuana cases]

• Order on Motion to Vacate Marijuana Conviction
• Order on Motion to Vacate Marijuana Conviction

Originally posted by @vritant24 in #22 (comment)

A new wireframe for the UI has arrived on 2019-09-25, we need to update our frontend code to match the new UI