Spike - Prioritized Errors

andrew-jameson commented 3 months ago

Description: Intended to develop a technical strategy for #3026 and ensuring a smoother UX for error report access. Also relates to #3075 for sys admin experience.

Open Questions:

Is this intended to prevent creation of lower-tier cat2/4 errors on the order of hundreds of thousands to improve backend performance? No, we will not prevent creation.
Do we want to halt parsing or continue through? No, we will not halt parsing.

Deliverable(s):

[ ] Development Design Document [need link]
[ ] Solution must ensure that error reports can be accessed by STT users regardless of parser error count

Supporting Documentation:

Proposed List of Validators -- has links to HHS resources, there are local copies below:
Manual Resubmission Results
Top 20 errors summary

lhuxraft commented 2 weeks ago

11/13/2024: Eric made code changes, reviewing with Alex before dev team re-review

lhuxraft commented 2 weeks ago

11/15: Feature changes discussed with Alex/Kathryn, needs one more review @andrew-jameson

lhuxraft commented 1 week ago

11/18: Miles and Victoria to take a look

lhuxraft commented 1 week ago

11/20: Miles/Victoria reviewed, Andrew to provide final review today

lhuxraft commented 4 days ago

11/25: Met with Kathryn on Friday, made a minor suggestion on capping the critical errors / assigning file status. Comment documented in the PR. Review will continue this week

raft-tech / TANF-app

Spike - Prioritized Errors #3155