Mets-reader-writer can eventually replaces the create_mets_v2 script during Ingest in Archivematica. In this instance that means when we write out to file, we can turn off the generation/output of the normative structmap. The normative structmap is used largely for documenting empty directories in Archivematica. It is a logical structmap (an abstract representation) vs. a physical structmap (what's actually there).
Current behaviour
There is no way to turn off normative structmap generation in mets-reader-writer according to the API: see wrte.
To output components of mets without the normative structmap a developer can serialize the structmap on its own using it's specific options: see serializing a structmap. The developer can then manually attach this to some other Elementree object.
Where do we see this in archivematica?
Right now, we're actually outputting a normative structmap at all times when we create the transfer METS file because that script uses metsrw: here
When we arrive at AIP METS generation it is optional whether or not we create a normative structmap: here. If we naively replace functions in this script with metsrw and ask the document to output itself to file, we will get this additional piece of XML.
Steps to reproduce
Create the simplest metsrw document, e.g. from the README.md:
Use this as a basis to try and change the flags and so forth for fun.
Transfer METS
Also, create a transfer METS, and download it. You will find a normative structmap, e.g. for Demo Transfer CSV (regardless of processing configuration options):
Expected behaviour
Mets-reader-writer can eventually replaces the
create_mets_v2
script during Ingest in Archivematica. In this instance that means when we write out to file, we can turn off the generation/output of the normative structmap. The normative structmap is used largely for documenting empty directories in Archivematica. It is alogical
structmap (an abstract representation) vs. aphysical
structmap (what's actually there).Current behaviour
There is no way to turn off normative structmap generation in mets-reader-writer according to the API: see wrte.
To output components of mets without the normative structmap a developer can serialize the structmap on its own using it's specific options: see serializing a structmap. The developer can then manually attach this to some other Elementree object.
Where do we see this in archivematica?
Right now, we're actually outputting a normative structmap at all times when we create the transfer METS file because that script uses
metsrw
: hereWhen we arrive at AIP METS generation it is optional whether or not we create a normative structmap: here. If we naively replace functions in this script with
metsrw
and ask the document to output itself to file, we will get this additional piece of XML.Steps to reproduce
Create the simplest
metsrw
document, e.g. from the README.md:Use this as a basis to try and change the flags and so forth for fun.
Transfer METS
Also, create a transfer METS, and download it. You will find a normative structmap, e.g. for Demo Transfer CSV (regardless of processing configuration options):
Your environment (version of Archivematica, operating system, other relevant details)
METRSW version
0.3.15
. AM version:1.11.x
onwards.Related issues
Transfer METS characterization output appears in AIP METS: https://github.com/archivematica/Issues/issues/1101.
For Artefactual use:
Before you close this issue, you must check off the following: