Backward compatibility for ingest spaces and publishing

Owned by Jasper Spruytte
Last updated: Jun 30, 2021 by Alexis Rombaut
1 min read

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.

Legacy Ingest

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)

Publication

When publishing a record the following changes are made to the following read-only Metadata Fields.

Field

Value

Description

Field

Value

Description

Internal.IsInIngestSpace

False

 

Administrative.RecordStatus

Published

 

Administrative.PublicationDate

2021-06-30T15:00:25.156000Z

The date is filled out with the current timestamp

REST API

  • In the MediaHaven REST API 2.0

    • Parameter publish triggers the publication when POSTing a record

    • Parameter autoPublish is marked as obsolete, it only causes Internal.IsInIngestSpace to be set to false

 

publish

autoPublish

 

publish

autoPublish

REST 1.0

Publication

Publication

REST 2.0

Publication

  • marked as obsolete

  • Only remove from ingest space

Â