Versions Compared

Old Version 4

changes.mady.by.user Alexis Rombaut

Saved on

compared with

New Version Current

changes.mady.by.user Alexis Rombaut

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

From version 24.3 the configuration is possible via the API

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

File formats

file_formats

Formats

  • List of Pronoms describing what the possible formats are for

represenations

  • representations

Overview

Pronom ID, Allowed, Forbidden, …

Transformations

transformations

  • Into which format with a particular

widht

  • width, height, dpi, bit rate etc to transform an original representation

  • For example, transformation into JPG (fmt/42) using 2000x2000 pixels

Transformation ID, Target Pronom ID, Extension, Width, Height, Dpi, Bitrate, etc

Storage Selection

The Pools on which to store the representations are determined by

Representation

Storage pool selection (cascade, first matching rule applies)

Original

  • Explicitly provided to the process media_tiered_ingest

  • Based on the setting ingest_default_mob_cluster_groups

Access

Transformations - Formats

file_formats_transformations_links

  • Which transformations to generate for a particular format

  • For example convert TIFF (fmt/353) into JPG (fmt/42)

Tranformation ID, Pronom ID

Transformations - Cluster groups

transformation_cluster_group_links

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 to failed

    • 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 to failed

    • The Administrative.RecordStatus of the data record, original representation and access representation will be set to Rejected

Info

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