Metadata Sidecar

Metadata Sidecar

Description

From 18.4 onwards MediaHaven uses a new sidecar format with a one-on-one correspondence with the metadata fields and metadata families. The sidecar format is now namespaced with two namespaces: one for the sidecar skeleton (mhs) and one for the MediaHaven metadata fields (mh). Note the version number in the namespace URIs. 

From 25.2 onwards the XSDs are also available directly on your installation using the Classification Metadata Sidecar.

Namespace MHS

Namespace MH

Using head for latest version

Since version 26.1, you can use head for <version> instead of specifying a concrete version (e.g., 26.1). This always points to the latest available Metadata Sidecar version.

Note: XSD files for head are only available on your own installation, not on https://zeticon.mediahaven.com:

  • https://<environment>/metadata/head/mh.xsd

  • https://<environment>/metadata/head/mhs.xsd

XSD files for specific versions are available on both https://zeticon.mediahaven.com and your own installation (from 26.1 onwards).

The namespace URIs remain unchanged and must still reference https://zeticon.mediahaven.com/metadata/<version>/mh/ (or /mhs/), even when retrieving XSD files from your own domain.

Strategy

An advanced feature is using the attribute strategy on a top-level metadata field: Metadata Strategy.

Versions

When the metadata format changes during a release, a new namespace with that release number will be present. However, you can still keep submitting using the namespace of the previous metadata versions. Note that not every release of MediaHaven (4 per year), will have a new metadata version, in which case the metadata version number keeps the version number of a previous release. 

MediaHaven has the following list of metadata versions

Backwards compatibility 

You can keep using the old format External Metadata [deprecated] with the system converting the old format into the new format under the hood. But we encourage the customers to switch to new formats because it will be default for the documentation and new features.