Archivematica–Dataverse integration (AM 1.18 / DV 6.7.1): ingest failure with Dataverse transformed files

[Federica Zanardini]

Hello Archivematica community,
I’m testing the integration between Archivematica 1.18 and Dataverse 6.7.1, and I’d like to share an issue we are encountering and ask whether others have seen similar behavior.
The ingest fails in the Dataverse workflow when the source Dataverse dataset includes files transformed by Dataverse itself, for example a .tab file generated from an original .csv.
Specifically:

- datasets containing only the originally uploaded files ingest correctly;
- datasets containing both original files and Dataverse‑generated files cause the workflow to stop at the “Dataverse METS XML” microservice;
the error reported is:

archivematica.MCPClient.clientScripts.parse_dataverse_mets.ParseDataverseError:
Exiting. Returning the database objects for our Dataverse files has failed

This suggests difficulties when resolving file objects described in the Dataverse METS, in the presence of transformed / derivative files.
In parallel, we have also posted a question to the Dataverse community to better understand whether Dataverse‑generated files (e.g. .tab) require special handling or filtering by downstream systems.
I’d be grateful for any insight on:

- whether this is a known limitation of the Dataverse transfer type,
- expected behavior regarding transformed files,
or recommended workarounds / configuration approaches.

Best regards,
Federica