Ingest Configurations
This feature is part of the release 26.1
Introduction
Installation-wide configuration of the ingest is already possible for many releases, but starting from 26.1, it will be possible to create several ingest configurations beforehand and specify them when uploading a new object.
Business Logic
An ingest configuration has the following properties
Property | Description | Default |
|---|---|---|
Id | Auto-generated unique UuiDv4 | - |
Organisation ID | An ingest configuration is linked with a specific organisation, or is shared installation-wide, in which case it is | <organisation of the user> |
Name | A unique name for the organisation, or across all organisations if it is installation-wide | - |
Default | Whether this is the default ingest configuration for this organisation, or installation-wide. At most 1 per organisation, and exactly 1 installation-wide ingest configuration | False |
Priority | https://mediahaven.atlassian.net/wiki/spaces/CS/pages/3949264897 jobs for the ingestion of the object will have this user priority → https://mediahaven.atlassian.net/wiki/spaces/CS/pages/3584589825. |
|
Storage selection | Determines the storage selection using the same mechanism available in METS. | - |
Transformations | Specific Transformations to apply for the ingestion of this object. By default, each provided transformation is only applied when the linked parent transformation is selected during the ingestion. By setting the transformation strategy to | [] |
API Support
When POSTing objects in the MediaHaven REST API an optional ingest configuration ID can be specified.