Feature: add a reusable, configurable temporal activity for file format validation

[fiver-watson]

Is your feature request related to a problem? Please describe.

• Multiple Enduro-using clients have requested an ingest activity that can validate the formats in a SIP against a controlled list (either allow or disallow, or in one case, a list for "warn" as well)
• Right now, this is done in a custom fashion for each client
• In the custom client example (here), the format list is hard-coded and cannot be easily modified
• Similarly, in the example above there is no easy way to use a disallow list instead

Describe the solution you'd like

• A reusable temporal activity for file format validation
• Is configurable
  • Can be configured to use EITHER a disallow or an allow list
  • Can be set up in Enduro to use different lists for different SIP / content types
• Will generate 1 PREMIS validation event for each file that passes

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:

• No disallowed file formats found

FAILURE:

• Content error: file format validation has failed. One or more file formats are not allowed: [list of paths/files]

PREMIS EVENT example:

<premis:event xmlns:premis="http://www.loc.gov/premis/v3" xsi:schemaLocation="http://www.loc.gov/premis/v3 http://www.loc.gov/standards/premis/v3/premis.xsd" version="3.0">
            <premis:eventIdentifier>
              <premis:eventIdentifierType>UUID</premis:eventIdentifierType>
              <premis:eventIdentifierValue>24c64e71-610a-4714-b79d-2a15294ca8a9</premis:eventIdentifierValue>
            </premis:eventIdentifier>
            <premis:eventType>validation</premis:eventType>
            <premis:eventDateTime>2024-05-09T14:19:50+00:00</premis:eventDateTime>
            <premis:eventDetailInformation>
              <premis:eventDetail>name="validate SIP file format against controlled list"</premis:eventDetail>
            </premis:eventDetailInformation>
            <premis:eventOutcomeInformation>
              <premis:eventOutcome>Pass</premis:eventOutcome>
              <premis:eventOutcomeDetail>
                <premis:eventOutcomeDetailNote>Format allowed</premis:eventOutcomeDetailNote>
              </premis:eventOutcomeDetail>
            </premis:eventOutcomeInformation>
            <premis:linkingAgentIdentifier>
              <premis:linkingAgentIdentifierType>URI</premis:linkingAgentIdentifierType>
              <premis:linkingAgentIdentifierValue>https://github.com/artefactual-sdps/temporal-activities/</premis:linkingAgentIdentifierValue>
            </premis:linkingAgentIdentifier>
          </premis:event>

[fiver-watson]

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.