Skip to content

Vermont extraction review: use neutral failure copy and court terminology from Vermont forms #168

Description

@nonprofittechy

Partner testing feedback

Vermont LITEFile testing on a laptop in Chrome. The current extraction-review language can sound as though the filer completed the form incorrectly or uploaded the wrong document when the system simply could not extract/match data.

  • @VTskier Replace We could not find any case details in your document. Enter them below, or go back and try a different document. with language like: Our system could not pull case details from your document. You can enter the details below, or go back and try a different document.
  • @VTskier Remove/replace We could not find this in your document. under individual choices for the same reason.
  • @VTskier Change We found a hint in your document, but we could not match it to a choice below. to We found a hint in your document, but could not match it to a choice here.
  • @VTskier For Vermont, call Court or county Court unit or county because Vermont court forms use “court unit,” and for most self-represented filers the unit is the county name.
  • @VTskier For Vermont, call Case category Court division, matching Vermont forms. Add plain-language examples such as Civil (including Small Claims) and Family (including Relief from Abuse) where they help users recognize the right division.

Code check / feasibility

These strings are currently hard-coded in:

  • efile_app/efile/templates/efile/extraction_review.html (no-details alert, Court or county, Case category)
  • efile_app/efile/static/js/extraction-review.js (the two per-field extraction/matching hints)

The Vermont jurisdiction config already exists and includes jurisdiction-specific metadata, so the Vermont labels/help can be made configurable rather than globally renaming concepts that may be called something different in Illinois or another state.

Proposed implementation

  • Use neutral, system-focused extraction failure language.
  • Make the court/category labels and optional explanatory examples jurisdiction-configurable, with sensible generic defaults.
  • Keep the underlying API/model names (court, case_category) unchanged; this should be a presentation/config change only.
  • Add tests for Vermont-rendered labels and the no-match/no-guess copy.

Acceptance criteria

  1. Extraction failure copy does not imply that the user or uploaded form is wrong.
  2. Vermont shows Court unit or county and Court division.
  3. Vermont can show examples such as Civil/Small Claims and Family/Relief from Abuse without changing API codes.
  4. Other jurisdictions retain their configured/generic terminology.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions