codeforpdx / recordexpungPDX

A project to automate the expungement of qualifying criminal records in Oregon. This project is done in conjunction with Qiu-Qiu Law.
https://recordsponge.com
MIT License
51 stars 89 forks source link

Show expanded charge type documentation in search results #797

Closed wittejm closed 4 years ago

wittejm commented 4 years ago

Edit: Renaming and updating this issue for the next phase, of adding the frontend feature.

See below for mockups.

To handle charge types that are essentially split between two classes (RomeoAndJulietIneligibleSexCrime and DUII), we'll need to address then in a way that both the Manual's charge types page and the entries included in the search results page both look "good" to the user, while the manual page is ideally still easily generated from the text written in the backend.


older, completed phase of writing the expanded documentation.

This will need to be a work in progress as we figure out exactly how to handle detailed explanatory documentation. We want to:

For now, we can achieve this by writing the explanation for a charge type as a string field on the charge type class object. The python doc module Phoenix relies on comment strings attached to classes and methods (obj.__doc__) but we should use a named string field because __doc__ strings are meant to be developer-facing, not user-facing.

The doc for each charge type can include the following:

The string field on each Charge type can be called expungement_rules

wittejm commented 4 years ago

We can work on this incrementally type by type, so y'all can feel free to spam smaller PRs for this issue.

hmarcks commented 4 years ago

Love this. Here's a proposal for revealing it on the frontend. Please take a look @michaelzhang43 and all:

Updated mockup below

wittejm commented 4 years ago

This looks great!

michaelzhang43 commented 4 years ago

Agree with Jordan. This looks great

One thing I’m concerned about is overexposing information and potentially confusing the user. For example, for a dismissed B Felony, I think our documentation should just be that any dismissed case is type eligible for expungement.

wittejm commented 4 years ago

That concern makes sense.

We already show the type eligibility reason which is usually very short. For dismissals we currently usually say "Eligible under 137.225(1)(b))" but there is an open issue #812 to clarify with "Dismissals are eligible under 137.225(1)(b))"

How about, to avoid overwhelming the user the link for more documentation should be a little "less welcoming" -- so the user doesn't click it thinking that they actually need that extra information. Maybe it's called "more legal details", then no one will click on it unless they really want to.

Maybe take the link off entirely, and it's only in the docs section of the website?

michaelzhang43 commented 4 years ago

How about one of the following:

  1. Citation
  2. Explanation
  3. Legal Citation
  4. Legal Explanation ?
wittejm commented 4 years ago

Todo: Identify and complete the set of charge types that don't have a rules string yet.

hmarcks commented 4 years ago

Updated mockup to account for multiple types when a charge needs clarification:

documentation1

wittejm commented 4 years ago

Showing charge rules in the results page was completed with #1324. I'll make a new issue for part 2, the standalone page of rules for all charge types.