CodeWithAsheville / CodeWithAsheville/zipcase
Develop a more robust name search workflow
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 0
- Avg merge
- 3h 41m
- Merged PRs (30d)
- 6
Description
The basic name search functionality that we have today does not serve the real-world use cases for _pro bono_ attorneys working on record expunction.
Must-haves:
- work around the 200-result limit (divide searches by counties if bumping up against the limit)
- provide post-filtering, where results are filtered after data retrieval (middle name/initial, birth year, _etc._)
- create and manage named sets of results under a client record
- add to results with another search (by case number or name; honor existing include/exclude settings when results overlap)
- remove from results (hide)
- show hidden results (current session only)
- new search (clear current working set, which is already saved)
- delete client (with "are you sure?" prompt)
- export client cases to .xlsx
- figure out the structure/navigation between search and case management — do we have _ad hoc_ and client modes on the search screens, or what?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.