Search: Practitioner-filed Brief Documents

[cholly75]

As a member of the public, so that I can easily find those briefs the Court has made visible, I need to be able to perform keyword and case searches for practitioner-filed briefs.

Last year the Court made the decision to have certain party-filed documents visible to the public. The criteria for this visibility were that the documents:

• were e-filed by practitioners on or after 8/1/2023 and are a specific document code (see attachment in Notes)
• or they are docketed as AMBR (amicus briefs)
• or they are supplements/amendments to or redacted versions of the above documents
• are not lodged, stricken, sealed, etc.

To provide further visibility into these documents, the Court would like to make them searchable via both keyword and case title/docket number, with a few filters (in the same way that Orders and Opinions currently are).

Put simply: the documents that the court made publicly visible with stories #9866, #10037, and #10076 should be searchable as a collection unto itself. This story has no new visibility criteria, and presumes the existing criteria remains in place.

Pre-Conditions

Acceptance Criteria

• All users - internal and external - have access to "Briefs Search"
• Searchable collection for Briefs Search includes ONLY the following non-sealed/lodged/stricken documents:
  • Documents with the attached event codes (see the Notes section for attachment) that have been e-filed by a practitioner on or after 8/1/2023
  • Documents with the AMBR event code
  • Documents with the following event codes IF they are linked to a document with any of the aforementioned event codes (see #10076 for reference):
  • AMAT
  • ADMT
  • REDC
  • SPML
  • SUPM
• User can search by/for any of the following values:
  • Case Title/Petitioner's Name - text
  • Keyword(s) - text
  • Docket Number - text
  • Filed Date - date range to/from
  • Filing Party - radio buttons
  • Selections available:
    • Commissioner
    • Other
    • All
• Search Results table includes the following columns:
  • Docket Number (with suffix)
  • Case Title
  • Docket Description
  • Filing Party
  • Filed Date
• Search results are ordered by Filed Date, descending
• Search results are hyperlinked in the Docket Number and Docket Description columns

Notes

• Do we need to scrape the documents' metadata prior to making them searchable?
• Documents in scope if e-filed by a practitioner on or after 8/1/2023:

Tasks

Test Cases

Story Definition of Ready (updated on 12/23/22)

The following criteria must be met in order for the user story to be picked up by the Flexion development team. The user story must:

• [ ] Is framed in business/user need, the value has been addressed.
• [ ] Includes acceptance criteria
• [ ] Has been refined
• [ ] Pre conditions have been satisfied.

Process: Flexion developers and designers will test if the story meets acceptance criteria and test cases in Flexion dev and staging environments (“standard testing”). If additional acceptance criteria or testing scenarios are discovered while the story is in progress, a new story should be created, added to the backlog and prioritized by the product owner.

Definition of Done (Updated 5-19-22)

Product Owner

• [ ] Acceptance criteria have been met and validated on the Court's migration environment
• [ ] Add scenario to testing document, if applicable (https://docs.google.com/spreadsheets/d/1FUHKC_YrT-PosaWD5gRVmsDzI1HS_U-8CyMIb-qX9EA/edit?usp=sharing)

UX

• [ ] Business test scenarios have been refined to meet all acceptance criteria
• [ ] Usability has been validated
• [ ] Wiki has been updated (if applicable)
• [ ] Story has been tested on a mobile device (for external users only)

Engineering

• [ ] Automated test scripts have been written, including visual tests for newly added PDFs.
• [ ] Field level and page level validation errors (front-end and server-side) integrated and functioning.
• [ ] Verify that language for docket record for internal users and external users is identical.
• [ ] New screens have been added to pa11y scripts.
• [ ] All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html.
• [ ] READMEs, other appropriate docs, and swagger/APIs fully updated.
• [ ] UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required).
• [ ] Interactors should validate entities before calling persistence methods.
• [ ] Code refactored for clarity and to remove any known technical debt.
• [ ] If new docket entries have been added as seed data to efcms-local.json, 3 local s3 files corresponding to that docketEntryId have been added to web-api/storage/fixtures/s3/noop-documents-local-us-east-1
• [ ] Acceptance criteria for the story has been met.
• [ ] If there are special instructions in order to deploy into the next environment, add them as a comment in the story.
• [ ] If the work completed for the story requires a reindex without a migration, or any other special deploy steps, apply these changes to the following flexion branches:
  • [ ] experimental1
  • [ ] experimental2
  • [ ] experimental3
  • [ ] experimental4
  • [ ] experimental5
  • [ ] experimental6
  • [ ] develop
• [ ] Reviewed by UX on a deployed environment.
• [ ] Reviewed by PO on a deployed environment. Can be deployed to the Court's test environment if prod-like data is required. Otherwise deployed to any experimental environment.
• [ ] Deployed to the Court's staging environment.

[katiecissell]

Pre-refinement notes:

• What does searching by 'keywords' mean in this context? These briefs are uploaded so we'd have to scrape the body text if we wanted that and that's not as reliable. - We need to make the body text searchable so whatever would make that happen

[katiecissell]

UX Notes:

WAITING ON FINAL DETERMINATION OF WHICH LAYOUT THE COURT PREFERS 8/5/24

Figma File

Add a new tab to the search page named Document after Case and before Practitioners. Orders and Opinions search will be moved into this new tab. Case and Practitioners search will not be changed. The documents tab will have some updated text of the date after briefs will be available to search. and also have radio options to choose what type of document to search by. The default document type will be Orders. The orders and Opinions radios will have their same search fields. Briefs will not have judge but have filed by radio options instead. The default filed by will be All.

Results:

Alternative layout:

[mwestereng1]

After story is completed, privacy policy needs to be updated to include "briefs"