Please describe the problem you'd like to be solved
At the moment it’s not possible to store the configuration settings with which a transfer is processed, other than by putting a (downloaded) processingMCP.xml file in the folder “submissionDocumentation” in the dataset (then it’s stored in the AIP within the folder with the same name). In v1.12 it is now possible to select a configuration file other than the default one when starting a Transfer. This opens the opportunity to save and store the information on the configuration settings with which a transfer was processed, preferably in the METS file.
Describe the solution you'd like to see implemented
Ideally this information would have to end up in an element in the METS file, for example Software agent information, and ‘translated’ from the standard UUID elements the configuration settings file (processingMCP.xml) consists of.
Describe alternatives you've considered
An alternative to storing the entire (‘translated’ or not) content of the configuration settings file would be to just store the name of the configuration file that was used, as derived from the info that is attached to the “start transfer”-button, in the METS file.
Additional context
This kind of logging would make life easier for Archivematica users/testers who often have to change workflows for processing datasets with different configuration needs.
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
commented
3 years ago
Please describe the problem you'd like to be solved At the moment it’s not possible to store the configuration settings with which a transfer is processed, other than by putting a (downloaded) processingMCP.xml file in the folder “submissionDocumentation” in the dataset (then it’s stored in the AIP within the folder with the same name). In v1.12 it is now possible to select a configuration file other than the default one when starting a Transfer. This opens the opportunity to save and store the information on the configuration settings with which a transfer was processed, preferably in the METS file.
Describe the solution you'd like to see implemented Ideally this information would have to end up in an element in the METS file, for example Software agent information, and ‘translated’ from the standard UUID elements the configuration settings file (processingMCP.xml) consists of.
Describe alternatives you've considered An alternative to storing the entire (‘translated’ or not) content of the configuration settings file would be to just store the name of the configuration file that was used, as derived from the info that is attached to the “start transfer”-button, in the METS file.
Additional context This kind of logging would make life easier for Archivematica users/testers who often have to change workflows for processing datasets with different configuration needs.
For Artefactual use:
Before you close this issue, you must check off the following: