Skip to end of banner
Go to start of banner

Backwards compatibility

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Introduction

MediaHaven is undergoing an internal restructuring head of the release of MediaHaven REST 2.0 API. A number of metadata fields will be changing in format. To maintain backwards compatibility the following services:

Will output the metadata in the fixed version 20.3 Metadata Sidecar 20.3 without ever increasing in version in future releases. Newly introduced metadata fields after version 20.3 will be absent.

MediaHaven REST API 2.0

The upcoming MediaHaven REST API 2.0 instead will always output the metadata in the latest version of the Metadata Sidecar as was before the case with REST API 1.0 which is now fixed at version 20.3.

OAI / Export with metadata

OAI and Export with metadata have now two additional metadata formats

Publishing

The following applies to releases 21.1 and later.

In MediaHaven 1.0 objects are first made available in an ingest space before being published by the user.

In MediaHaven 2.0 the concept of ingest spaces has been replaced by the introduction of the field RecordStatus. Records are first available in a draft status, and when published get the status Published.

To allow for a smooth transition between the two MediaHaven versions, objects published through the following legacy flows will also be published in MH 2.0:

  • Manual publishing in ContentUploader

  • Autopublish ingest space

  • Publishing in REST API 1.0 (manual + autopublish)

  • No labels