Searching USERS

Export Page

Dynamic Imaging Migration Guide

The Saas based Amplience Dynamic Imaging System enables you to migrate from your current system with no additional hardware setup or software installation. Migration will usually involve modifying your current asset upload workflow, and the way that your site makes rich media requests. In most cases these changes are likely to reduce repetitive tasks and maintenance, increased flexibility and reuse of rich media assets, and streamline the mechanism for having assets live on a scalable and resilient global content delivery network.
In order to help you consider the changes you will need to make in order to migrate to Amplience Dynamic Imaging this document describes how to request images for live use, and the standard workflows for getting your assets into the Amplience Dynamic Imaging System.
For further details, please get in touch with one of our Solutions Engineers or Implementation Consultants.

Requesting an Image

The Amplience Dynamic Imaging System (ADIS) is a dynamic imaging platform which uses standard HTTP commands to request image assets, and to control a multitude of the aspects of the returned image, such as size, format, quality, crop, sharpening.
HTTP request structure: : we advise that ADIS clients create a subdomain on their own domain and then configure a CNAME reference to the ADIS server. (This is usually setup with the client's IT/Infrastructure team working with Amplience Tech Support).

i/youraccount : this is established at account setup, and must be referenced by all image requests.

ImageID : The ID of the image asset being requested - this is the filename of the Image File minus the file extension.

.jpg?parameters : the apparent file extension is independent of the file type that was uploaded (and can actually be omitted altogether), putting .jpg or .png etc. will cause the Imaging System to generate the appropriate image format at request time. 

The querystring (all characters after the '?') can contain a multitude of parameters which can then be used to control numerous aspects of the requested image (dimensions, jpg compression, sharpening etc..)

Search Engine Optimisation
ADIS supports pre-processing rules, which means that you can request the same image in a multitude of ways, which can provide you with some very powerful mechanisms to support your Search Engine Optimisation strategy.
For example, these two URLs, actually lead to identical image requests:
Transformational Templates As well as requesting individual image control parameters in the querystring of an HTTP request, ADIS also support transformational templates. These are single querystring references which control a multitude of image commands, and which can be controlled and maintained through the ADIS Admin interface.For example:$lister_page$ Where $lister_page$ represents specific width, height, format, quality, sharpening commands etc. Ideally your implementation plan will consider using Transformation Templates: - page design categories i.e. Lister, Hero - to consider bandwidth specific variances (if device detection support it..)

i.e. lister_low_connection - to consider facilitating options around page load optimisation There are additional supporting documents that go into more detail around this, and are another key area to discuss with your implementation consultant.

Embedding a Viewer

A 'viewer' (or 'player') provides additional User Experience control on top of the Imaging System, such as Spin or Zoom. The ADIS Admin interface enables you to easily create viewer configurations, along with easy to use example embed code, which can be as simple as the following: 
Head- code
<link href="" rel="stylesheet" type="text/css" media="screen" />
<script src="" type="text/javascript"> </script>
<script type="text/javascript" src=""> </script> 
<img src="{MEDIA-IMAGE}?$hero_image$" id="zoom_inner" />
<script type="text/javascript">
amp.viewer("8cb46f05-7f24-41e6-a17b-3e727f364d67", {img:"MEDIA-IMAGE" , target: "zoom_inner"});


Please see Playground for new Viewer SDK details


Standard workflows for importing assets into ADIS

Standard rich media import workflows start with the rich media assets being upload on to an FTP account. Scheduled jobs can be set to import these assets hourly/daily/weekly and if it suits your workflow can be automatically set to be published straight on to the Content Delivery Network (CDN).

The connectors, scheduled jobs, and import configurations are all highly configurable and can be tailored to suit your business needs and creative workflows. Once these are established, many Business As Usual (BAU) processes can be undertaken without the need to log in to the ADIS back office system, and can simply require content creators to upload to an FTP, and Commerce/CMS systems to routinely synchronise with the ADIS Manifest.