Exports are an essential aspect of our platform to retrieve previously ingested objects by the Ingest Flows. Exports can be requested
The normal form of export is through [21.3] - Downloaden, delen en exporteren in the MediaHaven 2.0 front-end
API users can interact with the MediaHaven REST API to export records
A user can optionally define a name for the export. If not defined, the filenameExpression on the export location will be used to determine the name. See below for more info. When the expression yields a runtime error on evaluation, the original filename of the record is used. Other rules are:
illegal characters are replaced by a -
if the name exceeds the limit of 255 characters, the name is truncated
Export locations are predefined locations where objects can be exported to and have the following important properties
URI (protocol, server, credentials, path, etc)
Where to send the export, for example using FTPS or S3
Export options
Image
Document
Video
Audio
Metadata
Users require the function ADMIN_EXPORT_LOCATION to manage export locations.
Export options define additional transformations on the export files. If an export option is predefined on an export location, that option can not be removed or modified on the export request.
Option | Usage |
|---|---|
Metadata | Metadata can either be added as
|
Video | Transform the content into a video with particular transcoding options |
Audio | Transform the content into an audio with particular transcoding options |
Image | Transform the content into an image with with particular transcoding options |
Document | Transform the content into a PDF with with particular transcoding options |
See the https://integration.mediahaven.com/mediahaven-rest-api/v2/api-docs/index.html#mediahaven-rest-api-manual-export-locations-export-locations-object-structure for a complete overview of all properties which can be added to the export options for both exports and export locations.
24.3In version 24.3 a new property FilenameExpression is introduced that allows the user to dynamically determine the filename of an export by using metadata expressions. The structure of these expressions is the same as for Batch Metadata Expressions. You can find more info there.
The only difference from batches is that in this case, the input is a string instead of a sidecar. Consequently, the allowed fields are slightly different from those in batches:
Level | Case | Effect | Example Expression | Example Output |
|---|---|---|---|---|
Top | SimpleField | String |
|
|
Top | Others | Not allowed | ||
Sub | Child of MapField | String |
|
|
Sub | Other | Not allowed |