SPIKE: Store all statuses in holdings_status table?

While investigating issues related to holdings process, we noticed that it is difficult to trace logs for statuses -

Will it make sense to store all statuses in holdings_status table for each load and give the latest entry when requested from the GET endpoint? Will we clear out the table as soon as a process starts and populate fresh statuses for each load?

Outcome

• Determine approach
• Create a story IF the work can be estimated at 1 or 2 pts. Otherwise write up spike findings and we will consider in the future if more thant 2 pts estimated.

Timebox: 4 hours