Bug #13267

DIP upload doesn't work as expected when the METS file uses two PREMIS versions

Added by José Raddaoui Marín over 1 year ago. Updated over 1 year ago.

Status:NewStart date:02/26/2020
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Archivematica integration
Target version:-
Google Code Legacy ID: Tested version:2.5, 2.6
Sponsored:No Requires documentation:

Description

On #13067 and #13068, we tried to implement support for PREMIS 3 in a backwards compatible manner. However, those changes didn't consider the possibility of having 2 PREMIS versions on the same METS file and only the first namespace is used to parse its contents.

https://github.com/artefactual/atom/blob/qa/2.6.x/lib/QubitMetsParser.class.php#L29-L46

The start of a METS file containing both versions (generated in AM 1.9.2):

<?xml version='1.0' encoding='UTF-8'?>
<mets:mets xmlns:mets="http://www.loc.gov/METS/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/version111/mets.xsd">
  <mets:metsHdr CREATEDATE="2020-01-24T10:35:24"/>
  <mets:dmdSec ID="dmdSec_1">
    <mets:mdWrap MDTYPE="PREMIS:OBJECT">
      <mets:xmlData>
        <premis:object xmlns:premis="http://www.loc.gov/premis/v3" xsi:type="premis:intellectualEntity" xsi:schemaLocation="http://www.loc.gov/premis/v3 http://www.loc.gov/standards/premis/v3/premis.xsd" version="3.0">
          <premis:objectIdentifier>
            <premis:objectIdentifierType>UUID</premis:objectIdentifierType>
            <premis:objectIdentifierValue>2a401af1-4099-4580-b168-b119b17bcae5</premis:objectIdentifierValue>
          </premis:objectIdentifier>
          <premis:originalName>0124-2a401af1-4099-4580-b168-b119b17bcae5</premis:originalName>
        </premis:object>
      </mets:xmlData>
    </mets:mdWrap>
  </mets:dmdSec>
  <mets:amdSec ID="amdSec_1">
    <mets:techMD ID="techMD_1">
      <mets:mdWrap MDTYPE="PREMIS:OBJECT">
        <mets:xmlData>
          <premis:object xmlns:premis="info:lc/xmlns/premis-v2" xsi:type="premis:file" xsi:schemaLocation="info:lc/xmlns/premis-v2 http://www.loc.gov/standards/premis/v2/premis-v2-2.xsd" version="2.2">
            <premis:objectIdentifier>
              <premis:objectIdentifierType>UUID</premis:objectIdentifierType>
              <premis:objectIdentifierValue>debba95d-c1d9-47ab-a995-2504814912c5</premis:objectIdentifierValue>
            </premis:objectIdentifier>

I'm not sure in what version AM included the double PREMIS namespace but I believe that AM 1.10 uses PREMIS 3 across the entire METS file and that this shouldn't be an issue with that version.

History

#1 Updated by Ross Spencer over 1 year ago

The relevant issue for 1.10 is:

Other connected issues are:

Around the effort to normalize across versions.

NB. As being discussed in Slack there may be other issues around this to be discovered.

Also available in: Atom PDF