Specialized Usage : Using the Media Delivery Cloud : How it works
   
How it works
Publishing or un-publishing an asset in the Media Delivery Cloud is a matter of changing a value in the Media Delivery Cloud Request record field. Field values can be changed via the Desktop Client or the Web Client, but not via Portals.
Prerequisites:
You need to employ a Record View Set that contains the MDC-specific fields.
To initiate the publishing of an asset and/or master image:
 
1. Select the asset an open it in edit mode view (Web Client), or open its Information window (Desktop Client).
2. In the MDC Request field, select either Publish original asset, or Publish master image, or Publish original asset and master image.
3. Save your changes
On its next run, the Cumulus Scheduler reads the value in the MDC Request field and performs an appropriate action. The MDC state field value is updated accordingly.
Uploaded assets and master images are provide with an expiration date by default. As long as the Scheduler runs regularly, this expiration date will be extended automatically.
Un-publishing assets
Assets and/or master images can be un-published from the Media Delivery Cloud anytime if they are not longer needed.
To un-publish an asset from the Media Delivery Cloud:
 
1. Select the asset an open it in edit mode view (Web Client), or open its Information window (Desktop Client).
2. In the MDC Request field, select either Unpublish original asset, or Unpublish master image, or Unpublish original asset and master image.
3. Save your changes.
With the next run of the Cumulus Scheduler, the asset will be deleted from the Media Delivery Cloud.
File Versioning and the Usage of the Media Delivery Cloud
Checking in a new version of an asset file into Cumulus affects the asset creation date value. If triggers and scheduler tasks are set up properly, new versions of assets will be automatically uploaded to the Media Delivery Cloud on the next run of the scheduler.
If you do not want to automatically re-publish updated assets, you must not specify a field-specific trigger with the Media Delivery Cloud trigger action!