Backward compatibility for ingest spaces and 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.
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 https://mediahaven.atlassian.net/wiki/spaces/CS/pages/42074134.
Field | Value | Description |
|---|---|---|
|
|
|
|
|
|
|
| The date is filled out with the current timestamp |
The same logic applies for ingest in https://mediahaven.atlassian.net/wiki/spaces/CS/pages/2876997967 as for legacy ingest.
REST API
In the https://mediahaven.atlassian.net/wiki/spaces/CS/pages/2447769640 2.0
Parameter
publishtriggers the publication whenPOSTing a recordParameter
autoPublishis marked as obsolete, it only causesInternal.IsInIngestSpaceto be set tofalse
| publish | autoPublish |
|---|---|---|
REST 1.0 | Publication | Publication |
REST 2.0 | Publication |
|