The Media Delivery Tab

With the Media Delivery on Premise (MDO) option, Cumulus can act as a provider and distributor for assets. Renditions of cataloged assets can be integrated e.g. in web sites and accessed via specific URLs.

Use this tab to define:

• The Asset Action that will be performed on an asset to create the master image which will either be used to generate arbitrary renditions.

• The settings of the cache, that is, the amount of time d uring which a requested rendition is delivered out of the cache, before Cumulus checks for necessary updates, and the amount of disk space available for the cache.

NOTE: No MDO-specific trigger action available for MDO!
As this question came up repeatedly, please remember that Cumulus does not provide a specific trigger action for MDO, as it does for MDC. With the Media Delivery Cloud, this trigger action is used to synchronize certain altered meta data from the Cumulus Server to the MDC server. As there is no external server involved with the Media Delivery on Premise, there is no need for data synchronization — the MDO alway knows about the most recent meta data changes.

Asset Actions – a table with the asset actions that will generate master images. You can add more Asset Actions (from the Asset Actions available at the Cumulus Server), remove Asset Actions from the list, and define the order in which they will be performed, using the appropriate buttons.

If there are multiple Asset Actions listed, they will be performed in the given order. However, as soon as an Asset Action generates a result, the rest of the Asset Actions in the list is ignored. This behavior can be used to easily generate master images from different asset types, e.g. images or videos, that require different asset actions to generate them.

NOTE: Asset Actions – Required Settings
When defining Asset Actions for this purpose, make sure that you have specified appropriate pixel values for Width and Height in the Scale Dimensions Section of the Pixel Image Converter Parameters dialog. Additionally, the options: “Use Size as Bounding Box” and “Work at Image Size” must be activated, while the option “Enlarge Smaller Images” must be deactivated!

Catalog Alias – Select the desired Catalog Alias from those that are configured under Catalog Access on the Settings tab (for the Server displayed).

Radio buttons to toggle between the methods to identify assets and renditions. This value is necessary for 3rd party systems to build a proper MDO URL. If 3rd party systems don’t have access to Cumulus and therefore can’t retrieve the default values, a value from a different field can serve as identifier, e.g. an article number already known to the 3rd party system. Any field of type string or integer that is indexed for Sorting/Searching can be selected, however it is highly recommended to only work with values that are unique for all concerned catalogs. Otherwise, only the first found asset or rendition would be taken into account.

• Use default – By default, either the Media Delivery Cloud Asset ID (for assets), or the Media Delivery Cloud Image ID (for renditions), or the Unique Item ID (for both assets and renditions) can be used as item identifier in an MDO URL.

• Cache Expiration [s] – Time (in seconds) during which an asset and it’s renditions are delivered from the cache after the initial request. After that time, Cumulus checks whether the current rendition is still up-to-date, and updates it, if necessary.

• Fallback Image Cache Expiration [s] – Time (in seconds) during which a fallback image is delivered from the cache after the initial request. After that time, Cumulus checks whether the original asset or rendition is available again, and replaces the cache content.
The fallback image is used if the original image is not available for any reason. By default, the expiration time is the same as for the asset and rendition cache.

These values are only relevant, if the desired output format or compression quality is not specified in the URL that request the rendition.