Versions Compared

Old Version 11

changes.mady.by.user Bas Van den Steen

Saved on

compared with

New Version 12

changes.mady.by.user Alexis Rombaut

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Warning
titleDisclaimer

Complex objects are an advanced form of ingest workflow in MediaHaven which is not available to all customers. 

...

Tip

The value of the attribute ID must be a valid XML tag name which has the following rules:

  • Must start with a letter or underscore
  • Cannot start with the letters xml (or XML, or Xml, etc)
  • Can contain letters, digits, hyphens, underscores, and periods
  • Cannot contain spaces


Tip

Because the value of the attribute xlink:href must be a valid URI, you will have to URI encode its value if the path to the file contains illegal URI symbols such as ? % etc.

Step-by-step building of the METS

...

  1. ID: The value if of the type xsd:id which means it must be unique accross the XML document and it must start with a letter or underscore, and can only contain letters, digits, underscores, hyphens, and periods. More info here.
  2. CHECKSUMTYPE: Fixed value "MD5"
  3. CHECKSUM: The MD5 checksum of the referenced file
  4. USE: PRESERVATION, FIXITY, VIRTUAL, see Complex Objects Reference71282697 for more information.
  5. MIMETYPE: Optional parameter
  6. xlink:href: The path provided here must be relative to the root of the archive. See the concrete example archive below to evaluate this requirement. Using other values for path will cause the METS to be rejected because the referenced files will not be found inside the archive.
  7. ADMID:
    1. If you provide as value the ID of a mets:sourceMD in the METS, the embedded XML under this tag will be used a sidecar metadata for the referenced file. In the example above the values METADATA-SIP and METADATA-PDF refer to matching embedded sidecars in the format MediaHAVEN_external_metadata.
    2. If you provide as value the ID of a mets:digiprovMD in the METS, the embedded Premis event under this tag will be recognized by MediaHaven and be visible in the future metadata exports for this file. In the above example the values PREMIS-EVENT-01 and PREMIS-EVENT-02 refer to matching embedded Premis events.