Problem: it's unclear whether Transfer METS file has all the information required for a compliant AIP

peterVG commented 5 years ago

The Transfer METS file structure needs to be evaluated against information collected in issue #441 to ensure it will contain all the information required to restore backlog files from transfer storage as per issue #391.

Some required information may already exist in the current Transfer METS file, some may need to have a new location identified for them in the METS files, and some transfer metadata may not be needed to restore from backlog and therefore is not needed in the Transfer METS file.

An updated specification for the Archivematica Transfer METS file will have to be produced.

For Artefactual use: Please make sure these steps are taken before moving this issue from Review to Verified in Waffle:

All PRs related to this issue are properly linked 👍
All PRs related to this issue have been merged 👍
Test plan for this issue has been implemented and passed 👍
Documentation regarding this issue has been written and it has been added to the release notes, if needed 👍

sevein commented 5 years ago

@cole FYI we've seen empty PREMIS:OBJECT like the following:

<mets:amdSec ID="amdSec_828080">
  <mets:techMD ID="techMD_689086" CREATED="2019-03-22T13:54:27" STATUS="current">
    <mets:mdWrap MDTYPE="PREMIS:OBJECT">
      <mets:xmlData/>
    </mets:mdWrap>
  </mets:techMD>
</mets:amdSec>

Notice the empty <mets:xmlData/>.

When loading a METS like that via metsrw, we see:

metsrw.exceptions.ParseError: All mdWrap/xmlData elements must have at least one child; this one has none

sromkey commented 5 years ago

@evelynPM what do you think about looking at the new transfer METS and comparing to the METS specifications you recently wrote? If you feel like the new transfer METS gets a thumbsup from you, then this can be moved to done!!

sallain commented 5 years ago

A releasable increment of work has been completed on this issue; however, the work has not completely met the criteria of having all Transfer information in the METS. Decision has been made to de-scope this from 1.10 (rather than marking it as Done) as more work may be done on this issue in the future.

archivematica / Issues

Problem: it's unclear whether Transfer METS file has all the information required for a compliant AIP #442