Add a Report Tab to each AMI Set

[DiegoPino]

What?

Right now, given the fact that all runs on background/queue, we are passing errors happening during an AMI set ingest to the watchdog. Bad place for endusers to see/understand what failed/how it failed and what they may need to do to fix missing data/not found files, etc in their Source Data/AMI Set

Need

• Generate parseable reports that can be seen directly on each AMI Set
• Generate a Block on each User Landing page that we can use to show then Failed results, etc.

I need to investigate what is the best here. Watchdog is still good for us, but errors need to generate their own entries in each SET and we may want that to be "Views" processable or at least UI/UX facing for good.

@alliomeria will just tag you because this will eventually open some larger discussions about proper ways of reporting to users (in general) background processing and queue outputs, specially in our complex environment

[dmer]

from slack:
When I look at an AMI set in Content, I wish there was an easy way to see a list of the ADO’s in the set.
Something like an "Objects in this AMI Set" tab that has a list of the objects and indicates if they exist as ADOs in the repo or not.
Additional info like when the processing happened etc. would be nice additions, but the primary need is a list of the objects and their status (ingested or not).
Bonus - if the list can be links to the DAO's (if they exist)

[alliomeria]

Hello @DiegoPino --following up on discussions we had about this today. For this Report Tab, it may be helpful to be able to have QA checks for a set (such as when a set was updated/csv replaced, processed/reprocessed, LoD reconciliation progress, and potentially notes/flags).

[alliomeria]

Ping @DiegoPino 🙏 😸

[DiegoPino]

Ping received and working on it now

[DiegoPino]

Resolved