Search: Implement Plain Language Boolean Operators

[cholly75]

As a DAWSON user, I would like to be able to use plain language to search using boolean functions in keywords/phrases so I can perform more accurate searches.

Pre-Conditions

Acceptance Criteria

• Queries parse AND in the keyword/phrase field as the equivalent of the logical function AND/Elastic Search operator +

• Queries parse OR in the keyword/phrase field as the equivalent of the logical function OR/Elastic Search operator |

• Queries parse NOT in the keyword/phrase field as the equivalent of the logical function NOT/Elastic Search operator -

• Queries using plain language operators still correctly work in conjunction with other supported operators, such as " " for exact match - add example

• Plain language operators work everywhere that current ES operators currently work

• Instructional text available to user

Mobile Design/Considerations

IRS API Considerations

Do these changes impact the IRS API?

Security Considerations

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

Notes

• May require a great deal of regression testing for search
• Will need to update instructional text

Tasks

Definition of Done (Updated 4-14-21)

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 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)
• [ ] Interactors should validate entities before calling persistence methods
• [ ] Code refactored for clarity and to remove any known technical debt
• [ ] Acceptance criteria for the story has been met
• [ ] Deployed to any Flexion environment for UX Review
• [ ] Deployed to the Court's migration environment

[kkoskelin]

Code to parse natural language processing is on this branch: https://github.com/flexion/ef-cms/tree/8731-search-ustc-parser stand-alone file that does the magic is shared/src/utilities/searchSyntaxParser.js (and lots of tests, too)