cover case where dmdSec already has TEI, not MODS header

[bertsky]

DFG's METS-Anwendungsprofil (p. 22) also allows for the case where metadata is not in the form of MODS …

<mets:dmdSec ID=”dmd_1”>
  <mets:mdWrap MDTYPE=“MODS“>
    <mets:xmlData>
      <mods:mods>
        ...
      </mods:mods>
    </mets:xmlData>
  </mets:mdWrap>
</mets:dmdSec>

… but in the form of TEI …

<mets:dmdSec ID=”dmd_2”>
  <mets:mdWrap MDTYPE=“TEIHDR“>
    <mets:xmlData>
      <tei:teiHeader>
        ...
      </tei:teiHeader>
    </mets:xmlData>
  </mets:mdWrap>
</mets:dmdSec>

Perhaps we should support that case.

[bertsky]

@tboenig if I understand you right, this is not realistic, because TEIHDR is not as well standardized as MODS.

But you mentioned that sometimes being able to incorporate other information sources like MarcXML might indeed be useful. So that could be an optional input file, right?

(And we also briefly discussed IIIF manifests.)