Skip to end of banner
Go to start of banner

Backward compatibility for ingest spaces and publishing

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 3 Current »

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)

Technical

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

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

  • The same logic applies for ingest in [21.2] - Documentatie Mediahaven 2.0 as for legacy ingest.

  • In the MediaHaven REST API

    • Parameter publish trigger the publication when POSTing a record

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

  • No labels