Introduction
The following offers an overview of 4 concepts configuring how ingested items are transformed from their original representation into one or more access representations.
Configuration
Concept | Database Table | Purpose | Properties |
---|---|---|---|
|
| Pronom ID, Allowed, Forbidden, … | |
|
| Transformation ID, Target Pronom ID, Extension, Width, Height, Dpi, Bitrate, etc | |
Transformations - Formats |
|
| Tranformation ID, Pronom ID |
Transformations - Cluster groups |
| On which cluster groups to store the access representation created by the transformation | Transformation ID, Cluster group Pools |
Error handling
Access representation failure policy
The organisation setting failed_access_representation_policy
determines what happens when a transformation fails to generate an access representation.
There are two options:
SKIP
The default option
The
Internal.BrowseStatus
field of the data record and original representation will be set tofailed
The access representation itself will be deleted
The ingest flow simply continues
REJECT_PARENT
The
Internal.BrowseStatus
field of the data record and original representation will be set tofailed
The
Administrative.RecordStatus
of the data record, original representation and access representation will be set toRejected
For DAV the ingest will always behave as if option SKIP is selected.
Rejection policy
The organisation setting ingest_rejection_policy
determines when an ingest is rejected.
There are two options:
LENIENT
The default option
When an ingest happens with multiple children and a child fails, only that child has status
Rejected
, other objects will continue to be ingested.Administrative.Rejections is filled in for the child Record that has status
Rejected
.
FAIL_FAST
When an ingest happens with multiple children and one child fails, the complete ingest is
Rejected
.
/rejections endpoints returns the Administrative.Rejections of all children