We're testing the integration between Archivematica 1.18 and Dataverse
6.7.1, and we’d like to share an issue we are encountering and ask
whether others have seen similar behaviour.
The ingest fails when the source Dataverse dataset includes files
transformed by Dataverse itself, for example a .tab file generated from
an original .csv.
More in detail:
- 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. We’d be grateful if you have specific experience on this or similar problems.