DC 5.3.0 4.9 Sitecore Integration

Owned by Tobias Thornfeldt Wolters
Feb 13, 2020
4 min read

This page explains the steps of how to create an Integration Endpoint in Media Manager which handles Asset, Metafield, TreeValue and ComboValue for Sitecore.

Pre-requisites

Installing a DAM for Sitecore will be needed for creating an integration endpoint in MM. The following chapter has information on how to install DAM for Sitecore and also the basic use of Sitecore. (Digizuite™ DAM for Sitecore )

In ‘Administration DAM for Sitecore’ under the ‘Control Panel’, there is an option called ‘Digizuite Integration’. In this option, there is a list of all the Sitecore integrations.

The list shows some information about the endpoint such as the SitecoreURL, endpoint GUID, its status etc. If multiple endpoints are needed, it is very easy to create others:

Configuration

Login to MM and enter the ‘Settings’. On the left side, there is a menu with several options. Under ‘Integrations’ there is a list of all the integration endpoints created from MM. When creating a new Integration Endpoint, the setup varies depending on the ‘Export Type’. The picture below shows the integration setup for Sitecore. (Each of the inputs will be explained)

Title and Folder ID

The title of the integration endpoint could be anything the creator wants it to be. The ‘Integration folder ID’ points to a folder in DAM center and this folder is also available in Sitecore. So, whenever there are changes in the given folder ID, those changes will also happen in Sitecore via the endpoint.

The folder ID could either be from one that already exist or from a new folder. By right clicking on the folder and edit the folder rights, a new window will appear. This window shows the members who have rights to the folder, and at the top of the window, the folder Id is shown in parentheses after the folder’s name.

Export Type

There are four different export types:

  • ToFolder

  • ToMail

  • ToSitecore

  • ToYoutube

As mentioned before, the integration setups can vary depending on which export type is chosen. When choosing ‘Sitecore’, two other inputs appear after the Export Type input field– SitecoreApiKey and SitecoreApiUrl. Both are used to point to the endpoint created in ‘Administration DAM for Sitecore’.

Metadata type

Currently, there are two different types of transforming meta data – ExcelFile or Xml

Event, Metafields and Profiles

Each item type has different events and which of these events should export to Sitecore when triggered can be controlled by the user.

The same can also be done with metafields and profiles. Profiles can be used to specify a group of formats that can be supported. For instance, the profile’ OOBE Media Manager Image contains several different formats for images (Picture below).

Then for the ‘Export media format ID’, find one the corresponds to the formats in the profile. For instance, JPG big.

Reminder

There are some issues that has not been dealt with yet. For instance, the current integration setups are focused on assets alone, when the integration service now handles metafields, tree values and combo values.
Their events have not been included under ‘Subscribing to events’.

Another issue is the ‘Search name’ input. It is no longer needed. Depending on which item type(s) the integration endpoint handles, the necessary searches will be performed, without the user having in specify it.
Also, there is going to be another input field where the user must specify which item type(s) the integration endpoint has to handle.