Then activate the BS license for the BS Cloudinary Connector in the BS license settings.
Afterward, you should be able to provide the Cloudinary Connector settings in the global settings tree here:
from your Cloudinary account at
Settings / Security / Access Keys:
Preparing DAM Attributes for the Cloudinary ID and Preview
In the next step, you can create two attributes in the DAM attribute and class configuration:
The Cloudinary ID will be used to retrieve the unique identifier for the Cloudinary asset. Just create a simple single-line text field and make sure it will be available for all files that should be sent to Cloudinary.
The Cloudinary Preview is optional and can be used to preview the asset through the Cloudinary CDN. The attribute type must be “BS Cloudinary Preview” and is a special attribute provided with the Cloudinary connector module. When you scroll down here you can provide further settings:
Cloudinary ID Field: the field that holds the Cloudinary ID
Display: How the Cloudinary Image should be displayed.
Possible values for the display are:
Image: a preview image is displayed in the DAM editor
URL: the URL to the image is shown
Link: the URL to the image is shown as clickable link
For all previews here the Width and Height can be specified above.
Sending Images to Cloudinary
The actual synchronization between the DAM (leading) and Cloudinary (led) is implemented as BS Event Plugin. Read the article about the BS Event Queue first to understand the concept and how such queues can be configured:
Once the queue is set up, select at least the BS Cloudinary Connector as Event Listener and select the Cloudinary ID Field you have prepared:
The connector will now work as follows:
For each new DAM file a new Cloudinary file will be created and the new Cloudinary ID will be written back to the Cloudinary ID field of the Contentserv DAM asset.
For each updated DAM file the existing Cloudinary asset will also be updated. Please note, that only file content updates will trigger an update of the file content in Cloudinary. Normal meta data updates will not have any impact to avoid unrequired network traffic.
For each deleted DAM file the existing Cloudinary asset will also be deleted.
Once you have a Cloudinary ID in the DAM system it can be exported either as ID or through the Cloudinary Preview attribute as any other DAM field.