[DISCUSS] FY 25 - Tech Debt - Batch Processes - Th 6/27

[sshetenhelm]

Story Our team has recognized that we need to address issues with refactoring/refining batch processes as part of our FY 25 work. This ticket is intended to open the discussion about what work needs to be done.

Suggestions & comments that arose during our Technical Debt Brainstorming Session:

• Organize batches more consistently. Maybe move anything that's not used by multiple batches out of BatchProcess.
• Make it easier to add status/info/errors to batch processes
• Refactor how we get the admin sets for the batch process table.
• Batch process refactor.

Notes: Ex. file where different methods for batch processes, right now some stuff related to some jobs or related to all, this ticket talks about cleaning that up, making more compartmentalized, etc. Not easy to make it "clean"; could refactor process; how vital are status messages we have now? Most likely approach would be keep messages and that data, but "rip out the guts and make it reusable" and usually shorter; easy to understand and read; I don’t think we would need to change the schema / data table so we should be cool on keeping the data in line

Acceptance

• [x] Schedule a discussion to take place with pertinent team members (Wed, Fri, or Mon?)
• [x] Define what work needs to be done
• [ ] Construct backlog tickets for next steps