9.1 How to use a different user than admin to manage synchronization
If using an already existing user as the one who can create/sync silos other than admin / b, then enable autoCreateDigizuiteMember. Once the DFS module is installed and configured:
- Login to Sitecore
- Go to User Manager
- Edit the user and add these 2 roles to the user
- Sitecore\DFS
- Sitecore\ Digizuite DAM for Sitecore Administrators
- Log out and then login with the user again. Now the user will automatically be created in the Digizuite™ DAM Center and should be able to create/synchronize silos.
9.2 Access key cache
By default, the access key from Digizuite™ DAM Center is cached for 5 min. The setting can be changed in DFS.settings.config.
<setting name="DFS.Connect.LogonCache.TimeToLiveInSeconds" value="300" />
The Digizuite™ DAM Center also has a configuration about how long an access key lives. By default, it is 24 hours. It is important that the Digizuite access key period is greater than the Sitecore access key cache period.
9.3 How to configure which metadata to show in the asset preview area (Dam Explorer and Asset browser)
It is configuable which metadata that is showing in the asset preview area. It can show standard data about the asset, like width, height, file size etc. It can also show custom made metadata that is bound to the asset. The custom made metadata is configured in Digizuite™ DAM. Remember that the custom made metadata can only be used in the module, if they are synchronized into Sitecore.
The configuration is located in this file: /App_Config/Include/damforsitecore/DFS.Settings.config under the section <DFS.AssetPreview.Metadata>.
This is the default configuration.
<DFS.AssetPreview.Metadata>
<metadata dictionaryKey="description" field="Description" type="note" />
<metadata dictionaryKey="filesize" field="FileSizeAbbreviated" />
<metadata dictionaryKey="width" field="ImageWidth" append=" px" />
<metadata dictionaryKey="height" field="ImageHeight" append=" px" />
<metadata dictionaryKey="videowidth" field="VideoWidth" append=" px" />
<metadata dictionaryKey="videoheight" field="VideoHeight" append=" px" />
<metadata dictionaryKey="duration" field="VideoLength" />
<metadata dictionaryKey="typename" field="AssetTypeName" />
<metadata dictionaryKey="importedby" field="ImportedBy" />
<metadata dictionaryKey="importeddate" field="CreatedDateTime" type="datetime" />
</DFS.AssetPreview.Metadata>
Valid xml attributes for the metadata tag are: dictionaryKey, field, type, append and metafieldId.
You wont have both field and metafieldId in the same metada tag, only one of them.
| Name | DescriptionDescriptionDe |
|---|---|
| dictionaryKey | This is the key pointing into a dictionary located in the core database. |
| field | These are the standard values about an asset, like width, height, file size etc. The valid list fields are: AssetId, AssertName, AssetTypeId, AssetTypeName, Filesize, FilesizeAbbreviated, ImportedBy, CreatedDateTime, ChangedDataTime, Extension, VideoLength, VideoWidth, VideoHeight, |
| type | At this current implementation we have 3 valid types:
|
| append | Will append to the value, ex. width we append " px", will look like this 244 px. |
| metafieldId | These are the custom metadata, defined in Digizuite™ DAM. The custom metadata can be found under this location in the master database. To determine the type, by the DatatypeId. |
9.4 Define which fields free text search in (DAM Explorer and Asset Browser)
By default freetext search in DAM Explorer and Asset Browser searches in these fields: assetid, name, description, extension, importedby, assettypename. This cannot be changed. You have the option to add more fields to the freetext search.
The configuration is located in this file: /App_Config/Include/damforsitecore/DFS.Settings.config under the section <DFS.AssetSearchableMetadata>.
To add a custom metadata fields, you inset this tag: <metadata dataTypeId="" fieldId=""/>, the fieldId is the Item ID and the dataTypeId can be found on the metafield item.
The custom metafields can be found under this location in the master database. /sitecore/system/Modules/Digizuite/MetaDataRoot/MetaGroupRoot Each of the items, has a field called dataTypeId.
By default the <DFS.AssetSearchableMetadata> section is empty.
Example with one extra field.
<DFS.AssetSearchableMetadata>
<metadata dataTypeId="60" fieldId="{D87A8D4A-89E8-70D4-9036-DDA294C6B8D2}"/>
</DFS.AssetSearchableMetadata>
In order to see the changes, you have to rebuild the index (dfs_assets_master_index).
9.5 Video player (JQuery 2.1.4 conflicts)
The default configuration uses a custom video player called FlowPlayer. This is provided by Digizuite. This uses JQuery 2.1.4 which can sometimes conflict with existing Sitecore sites. To diable this leave the following tag blank:
<setting name="DFS.EmbedPlayerScriptInclude"> <patch:attribute name="value"></patch:attribute> </setting>
This fallbacks to the default HTML5 player, but then no JQuery is used.
9.6 Auto synchronization of assets
DAM For Sitecore has a pipeline that synchronizes assets automatically. Sometimes on larger Sitecore instances this synchronization misses some assets due to workload on the server. If this behavior is experiences, one can try tweaking the following parameter:
<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
<sitecore>
<settings>
<setting name="DFS.AssetSiloSettings.Default.OverlapOnSiloSync" value="2" />
</settings>
</sitecore>
</configuration>
This parameter adds an overlap on the automatic silo synchronization such that the period for which asset updates is asked is extended by that value. It means that assets that may be missed in the first run, is synchronized next run. The value is in minutes.
Table of Contents