Open fiver-watson opened 5 months ago
NOTE: after a meeting today (2024-06-05) with SFA to gather feedback on PoC#1, I have edited the desired solution bullet points in the description above, to add 👍
Can be set up in Enduro to use different lists for different SIP / content types
SFA tried running a SIP type not yet supported (a SIARD sample). In reviewing the sample package, we discovered that there are formats included in there that are disallowed for VECTEUR AIPs / SIPs. Consequently, it seems like there will be different allowed / disallowed formats for different SIP types. We should take that into account when designing and developing this feature.
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Describe alternatives you've considered
Continuing to create custom temporal child workflows for every client? :thinking:
Additional context
It should also make use of any reusable patterns for displaying task outcomes in the Enduro UI that might be developed as part of this Enduro issue 949
Proposed outcome messages:
SUCCESS:
FAILURE:
PREMIS EVENT example: