Content Comparison

After installation of the NuGet package, it's time to setup the connection to you Digizuite DAM instance. Add the DAMIntegrationConfiguration to your startup class. The configuration should be added after the AddCms due to TinyMCE initialization.

Code Block

language	c#

  services.AddDigizuiteDAM(
                new Digizuite.Optimizely.Configuration.DAMIntegrationConfiguration()
                {
                    DatabaseName = "alloy_mvc_netcore",
                    Connection = new Digizuite.Models.DigizuiteConfiguration()
                    {

                        BaseUrl = new Uri("https://dam.wellspect.com/"),
                        SystemUsername = "Episerver",
                        SystemPassword = "55f2f63f09ff4f73f75fbb7d7e6e69b0",
                        ConfigVersionId = "/5/"
                    }
                });

Main Digizuite Element

...

DAMIntegrationConfiguration parameters

Name	Type

Name

Required	Default	Description

string

Connection

baseGuid

DigizuiteConfiguration

No(a hardcoded guid)A guid that is used as the 'foundation' to generate all the assets Content Guid. Usually you won't have to change this.stringnameNo""The name with which the integration identifies itself - for example when sending editor notificationsboolredirectvideostreamNofalseDefault behavior is to have Episerver act as a video proxy for video assets. If this is set to true, Episerver will instead redirect the video streams to the DAM directly.booldisablenotificationsNofalseIf set to true, will supress editor notifications from the integration.boolautoattachNotrueControls if the Digizuite Content Provider should automatically attach after initialization to an entry point automatically created. If this is false, you will need to manually configure the content provider.stringautoattachnameNo"Digizuite"The name of the entry point automatically created in Auto Attach mode.stringvalidFullSearchNamespacesNoEPiServer.Find.Cms.ContentIndexer,EPiServer.Find.Cms.IndexingJobServiceComma-separated list of valid namspaceses. Here you add the valid namespaceses that are allowed to do a full search and requesting all assets from Digizuite through our DigizuiteContentProvider. By default is is only the Find indexing that are allowed.boolpreventdigizuitemediatypesinepiserverfolderNotruePrevent that Digizuite media types can be uploaded to a Episerver media folder.

...

Yes		This object contains the connection parameters to the Digizuite DAM instance.
RoleMappings	List<RoleMappingElement>	No

Child element: DigizuiteConfiguration

The connection is the most important child element. This is where the main connection setting pointing to the DAM is specified. Typically you will replace this with connections settings you have gotten from your own DAM Center.

secret

Name	Type	Name	Required	Default	Description
stringBaseUrlbaseUrl	Uri	Yes		Base url to the DAM Center
SystemUsername	string	user	Yes		Sync user that the integration can use in the DAM Center
SystemPassword	string		Yes		The hashed secret that the integrations sync user should use.
ConfigVersionId	string	versionId	Yes		A DAM Center can have many different products: Media Manager, DAM for Sitecore, Adobe Connector, Office Connector, etc. Each of these can have many versions. These versions facilitate having different configuration, searches, and other things, which can change the experience for the end user. These various versions are defined by their versionId. If the original version has versionId "/1/", then its first child will have "/1/0/". The versionId is an SQL data type called hierarchy ID. It is a tree structure. A use case may be that you want to experiment with some configuration, so you create a new version of DFE in the DAM Center. Then you can alter the versionId attribute on your EPi Server site to "/1/0/", and do your tests, while your public DFE integration still use the "/1/" versionId.

Child element:

...

The cache element controls the caching - both binary on-disk caching as well as some of the in-memory asset meta-data caching.

...

Child element: media

The media element defines the default media formats (DAM Center ID's) to retrieve if nothing else is specified. Usually the default settings will be sufficient.

...

Child element: mediaManager

If you have a Media Manager (version 5 or later) configured on your DAM Center, the integration to Episerver supports showing deep links to assets there. In order to do that, you must set the base url to the Media Manager.

...

Child element: roleMappings

RoleMappings

Since access rights can be set on individual assets in the DAM Center, you can use the list of roleMappings to map DAM Center roles to Episerver roles in order to ensure proper permissions for various editor groups. The default configuration of these elements should be sufficient in most cases.

Type	Name	Required	Default	Description
string	DigizuiteRole	Yes	n/a	The name of the role in Digizuite to map.
List<string>	EpiserverRoles	Yes	n/a	A comma separated list of Episerver roles that be given similar permissions to the Digizuite Role.

...

Type	Name	Required	Default	Description
string	documentType	Yes	n/a	The icon for the document type - for instance "video" for a video icon.
string	extensions	Yes	n/a	A comma separated list of file extensions to map for the above document type.

Child element: digizuiteIntegration

The digizuiteIntegration is used to setup the connection between Episerver and Digiziuite and listen for events in digizuite whenever an asset is updated. It is important that the guid is set and atleast one ot the chagetypes is added to the subscriptions property.

Each element in this list has the settings below:

...

Child element: cdn

If you want a cdn provider in front of your assets. These settings is only supporting the assettype video.