Problem: Dataverse agents do not make it into the backlog/transfer METS

[ross-spencer]

Expected behaviour

Information generated about a transfer during the transfer workflow is available in the SIP generated that is sent to Backlog (and in the AIP as the transfer METS file).

Current behaviour

When a Dataverse transfer is initiated an agents.json file is generated describing the external source (Dataverse instance) from which the dataset originated. This is consumed by parse_dataverse_mets.py which adds information about the files in the dataset and the lining agent information to the database. When we come to look at the backlog/transfer METS this information isn't available.

Steps to reproduce

1. Initiate a Dataverse transfer, either by configuring the space, or using the Sample Data.
2. Either send the SIP to backlog, or wait for an AIP to be created.
3. In the first instance, try and seek out the agent information from the Dataverse dataset and you will not be able to find it.
4. In the second instance, repeat 3. for the transfer METS and the information will not be there. Then compare that to the AIP METS and the information will be available.

Your environment (version of Archivematica, operating system, other relevant details)

Additional context

It might be enough to reorder the microservice job so that it appears before the METS.xml is generated for this to be fixed so that users have all provenance and technical information available that was generated in SIP bags. See below, it currently runs after that particular job:

AMAUAT tests for Dataverse might be updated to explicitly test for an agent, depending on the outcome of #1043. Dataverse tests were added as part of PR #143.

Related to: https://github.com/archivematica/Issues/issues/781 Related to: https://github.com/archivematica/Issues/issues/1043 Related to: https://github.com/archivematica/Issues/issues/45

---

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 (if applicable)
• [ ] Details about this issue have been added to the release notes (if applicable)

[sromkey]

We're not considering this a supported workflow but the docs should reflect that.