Digimetrics integration

59.4.9.1 Basic settings

The parameters present here can be compiled by entering relevant data regarding how the action will be performed.

Identification and Appearance
Name: It usually starts with the "Digimetrics Aurora Quality Check" string to indicate an Aurora action related to the information handling (e.g. Aurora Quality Check on NLE).
English name: If the previous name is given in a non-English language, insert its translated version here for the easiest multilingual recognition.
Color: Indicate the colour to display the action block in the T-Workflow Designer section.
Description: Insert a brief text explaining what the action is intended to do.

Behaviour
Concurrent processes: This parameter indicates the number of instances (by default, only one) of the current action that each Etere Data Mover server will be allowed to run contemporaneously.
NB: Etere suggests using concurrency, for example, if the current action will be used simultaneously by various T-workflows or if the source and destination count with a wide bandwidth.
Run each task using a separate agent process: Etere Data Mover will launch each instance of the current action in a separate Etere Data Mover agent, thus avoiding possible concurrency issues. Etere suggests enabling this parameter in case of high concurrency.
NB: Please note that detailed information on concurrency and agents is available in the Distributed concurrent processing section of the Etere Data Mover chapter.
Maximum Bandwidth: The max. bandwidth option is only supported for multistep copies to limit the bandwidth used for data transfers.
Do not use media folders even if configured: If disabled (by default), the file transfer will be performed by reading the source/destination paths from the selected metadevice's media folder (i.e. etereweb path); otherwise (if enabled), it will be performed by reading the tracks directly from the database (i.e. media folder for the asset forms).
NB: Please note that media folders are available only for DataMover actions that read data (i.e. files/paths) from the database (e.g. multistep copy, transcoding, etc.).