Internal User: Document keyword search

[mariahkannenberg]

As a Court User, in order to locate relevant documents, I need the the ability to search for the body of PDF documents by keyword.

Preconditions:

3913 is completed

Acceptance Criteria

• Internal Court User has the ability to search the body and metadata of court-generated documents system-wide by keyword
• Internal Court User has the ability to search metadata for externally filed documents system-wide by keyword
• Internal User should be able to narrow search by:
  • Date Range
  • Case (Docket No.)
  • Judge -- for Orders (post mvp)

Security Considerations

• [ ] Does this work make you nervous about privacy or security? No.
• [ ] Does this work make major changes to the system? Yes.
• [ ] Does this work implement new authentication or security controls? No.
• [ ] Does this work create new methods of authentication, modify existing security controls, or explicitly implement any security or privacy features? No.

Notes

• Not considering OCR in this story.
• For court-created documents, we can search the content. But for externally-filed documents we won't be indexing the content.
• Legacy data is searchable - was OCR'd
• Indexing and storing document data - potentially expensive (computing resources and dollar value)
• Where are we going to store the data?
• https://aws.amazon.com/blogs/compute/indexing-amazon-dynamodb-content-with-amazon-elasticsearch-service-using-aws-lambda/

Note: Include Decisions in document search

Tasks

Definition of Done (Updated 1-30-20)

Product Owner

• [ ] Acceptance criteria have been met

UX

• [ ] Business test scenarios to meet all acceptance criteria have been written
• [ ] 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
• [ ] 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, JSDocs 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)
  • [ ] Module dependencies are up-to-date and are at the latest resolvable version (npm update)
  • [ ] Errors in Sonarcloud are fixed https://sonarcloud.io/organizations/flexion-github/projects
  • [ ] Lambdas include CloudWatch logging of users, inputs and outputs
  • [ ] Code refactored for clarity and to remove any known technical debt
  • [ ] Deployed to the dev environment
• [ ] Deployed to the stage environment

[waldoj]

Although I agree that this work makes major changes to the system, I do not think that those changes pose a security concern that require any additional guidance or accommodation. This story will not require any additional review for acceptance or security review, beyond our normal processes.

[alsmith1]

[alsmith1]

DRAFT Test Scenarios

Scenario 1- Internal Court User has the ability to search the body and metadata of court-generated documents system-wide by keyword

1. Log in as an internal court user
2. Navigate to Advanced Search
3. Verify a document tab displays
4. Enter a search (keyword(s), docket number, Case name…)
5. Click search
6. Verify the results in the table below are listed with the following columns
   1. Docket number
   2. Case Name
   3. Filings and proceedings
   4. Pages
   5. Date
7. Verify in the results court generated documents display Expected result
   • [ ] Search page displays
   • [ ] Search page includes a Document tab
   • [ ] table below lists the following columns
     1. Docket number
     2. Case Name
     3. Filings and proceedings
     4. Pages
     5. Date
   • [ ] Court generated documents display

Scenario 2- External Users and general public do not have the ability to search the body and metadata of court-generated documents system-wide by keyword

1. Log in as an external user or general public
2. Navigate to Advanced Search
3. Verify there is no tab for Document Expected result
   • [ ] Search page displays
   • [ ] Search page does not include a Document tab

Scenario 3-Internal Court User has the ability to search metadata for externally filed documents system-wide by keyword

1. Log in as an internal court user
2. Navigate to Advanced Search
3. Verify a document tab displays
4. Enter a search keyword
5. Click search
6. Verify the results in the table below are listed with the following columns
   1. Docket number
   2. Case Name
   3. Filings and proceedings
   4. Pages
   5. Date
7. Expected result
   • [ ] Search page displays
   • [ ] Search page includes a Document tab
   • [ ] table below lists the following columns
     1. Docket number
     2. Case Name
     3. Filings and proceedings
     4. Pages
     5. Date
   • [ ] Externally generated documents display

Scenario 4-Internal User should be able to narrow search by:

• Date Range (MM/DD/YYYY) to (MM/DD/YYYY)
• Case name
• (Docket No.)
• Judge -- for Orders

1. Log in as an internal court user
2. Navigate to Advanced Search
3. Verify a document tab displays
4. Enter a search keyword
5. Click Search
6. Verify the results in the table below
7. Enter in a term for Docket number, case name, date)
8. Click search
9. Verify the search results narrow down with the additional search fields entered
10. Expected result
    • [ ] Search page displays
    • [ ] Search page includes a Document tab
    • [ ] Search results display with external and internal court documents and are narrowed by keyword
    • [ ] Search results narrow down to include new search terms

Scenario 6-If no results from search, default message displays

1. Log in as an internal court user
2. Navigate to Advanced Search
3. Verify a document tab displays
4. Enter a search (keyword(s), docket number, Case name…)
5. Click search
6. Verify table does not display instead “No Matches Found” message displays Expected result
   • [ ] Search page displays
   • [ ] Search page includes a Document tab
   • [ ] “No Matches Found” message displays

Scenario 7- When user clicks on a link under Filings and proceedings PDF view of Document opens in a new tab

1. Log in as an internal court user
2. Navigate to Advanced Search
3. Verify a document tab displays
4. Enter a search keyword
5. Click Search
6. Verify the results in the table below
7. Click on one of the result links under filings and proceedings

Expected result

• [ ] Search page displays
• [ ] Search page includes a Document tab
• [ ] Search results display with external and internal court documents and are narrowed by keyword
• [ ] PDF view of document opens in new tab