Problem: We haven't an in-built mechanism to verify an AIP's structure or compliance

[ross-spencer]

Please describe the problem you'd like to be solved

Artefactual tests an AIP structure extensively in the lead-up to a release. We have relied on the PREMIS in metadata validator up until recently. But that ticket shows the validator is behind as we start using newer standards.

Archivematica has mechanism to validate a bag, but a bag once created can have pretty much any structure within the bag 'envelope'. If something happens to the folder structure between moves, and an AIP is still created then it is difficult to spot the anomaly.

Archivematica doesn't have an inbuilt mechanism to perhaps do a handful of things:

• Validate the AIP METS.
• Validate the directory and file structure, e.g. if the directory and files in the METS still exist in the AIP.

Describe the solution you'd like to see implemented

Create a new microservice group with various AIP validation tasks. Starting with a validate METS task, possibly using metsrw's validation mechanism. Then we can build out to detect structure/layout anomalies.

This ticket could be an epic for further related tasks.

Describe alternatives you've considered

Leaving things as they are is always an option.

Additional context

We have documentation in the works around AIP structure, and we have a number of related tasks, some of which are starting to realize this capability:

• AIP structure page is out of date
• AMAUAT tests the content/structure of AIP METS
• AMAUAT confirms the content/structure of an AIP
• AMAUAT tests the content/structure of AIP

And there are related issues:

• It is possible to end up with a SIP that has no files
• There is an upstream issue with PIM validation of PREMIS 3
• We need to audit the metsrw validation capability
• Archivematica does not validate the AIP METS

This ticket could be an epic for further related tasks.

---

For Artefactual use:

Before you close this issue, you must check off the following:

• All pull requests related to this issue are properly linked
• All pull requests related to this issue have been merged
• A testing plan for this issue has been implemented and passed (testing plan information should be included in the issue body or comments)
• Documentation regarding this issue has been written and merged
• Details about this issue have been added to the release notes

[ross-spencer]

Closing as this is another non-issue from me I am afraid. Well, at least it only has a minimal potential to ever happen, i.e. an AIP with no files in the objects folder.

The verify AIP task runs on all AIPs created by Archivematica and looks to verify the checksums generated by the service via the database and the objects on disk here. The bag structure should be valid and the checksums should match.