Back link redirects user to the page he was before

The header corresponds to the following metadata : Name + Photograph.

The configuration can be changed with the metadata of your choice.

Next / Previous button

allow navigation to the next

or previous asset details following the order of the search results

Out of the box, Metadata section contains 3 sections :

• Information

• : Name

• , Caption, Keywords, Folder, Langue de l'

• asset, Collection

• , Organization

• Negociated Rights

• : Photograph*

• , Right types

• , Shooting date

• , Expiration date*

• , Authorized Channel

• Technical information

• : Asset type

• , Orientation

• , Dimensions

• , File size

• , Duration

• , Colorspace

• , Clipped.

Properties display depends on the property type.

The configuration can be changed with the sections and metadata of your choice.

Contains all information calculated by Artificial Intelligence : Keywords, and specific information for video like transcript of the video, identified objects and concepts.

In this area, the user can see the asset and play it (if it is a video, an audio file, or 3D). It has several additional options: zoom, full screen.
The configuration can be modified to include sharing on social networks.

Number of Views and downloads for the asset.

The configuration can be modified to hide these information.

Actions for an asset are : 

• Image / Video edition

  • Configure image edition by client

• Metadata edition

• Board management

• Download

Additionnal actions can be activated in the configuration :

• Reverse Search (with agreement of sales)

• Embed code generation (with agreement of sales as it is related with DXM option)

• Social Sharing

None of these sections come with the starter kit.

Assets can be linked with multiple options :

1. Fulltext request

2. Request on one or more metadata of the consulted asset

3. Request on links between assets

The configuration can be changed to activate these sections which are displayed under the asset.

$dam.details.defaultCursorConfig.defaultAssetDetailMeta.column[0].tabs[0].i18n

asset.assetInformation.label

I18n label to display as a tab title

$dam.details.defaultCursorConfig.defaultAssetDetailMeta.column[0].tabs[0].auto

Use data model to handle the details display of column[0].tabs[0]

$dam.details.defaultCursorConfig.defaultAssetDetailMeta.header.config

An array of fields to be displayed in the header section of a detail page.

A field can be either a string for simple configuration or referencing a named config. You can use an object for more precise configuration.

$common.namedDisplays.defaultAssetDetailTabAssetInsights.config

An array containing the tabs to display:

• assetInsightsAiLabels will display objects

• assetInsightsAiKeywords will display the concepts

• assetInsightsAiTimeline will display the timeline.

$edit.

default.

fields.

names.

dteendrights

Adds a number of days/weeks/months/year to the date.

Properties:

• args: array of 2 elements (1 when using endOf method). the first element is a number and the second element is a string reprensenting the unit of time (days, weeks, months, years, ...).

  Code Block
  language json
  # Example of uses "args": [10,"days"], # or "args": [2,"weeks"], # or "args": [6,"months"], # or "args": [1,"years"],

• autoDisplayUnit: by default, the text displayed will be "humanized" to be user-readable-friendly. If you'd rather display the time reference in another unit of time, you can specify it here. If no time unit is specified, it will take it from the args property.

  Code Block
  language json
  # Use case example { "default": { "helpers": [ { "autoDisplayUnit": "months", "args": [6,"months"], "method": "add" }, { "autoDisplayUnit": "months", "args": [1,"years"], "method": "add" }, { "autoDisplayUnit": "months", "args": [2,"years"], "method": "add" } ] } }

  Without the autoDisplayUnit, this is what we would have:

  Image Added

  By adding the autoDisplayUnit, we can have a unified unit of time:

  Image Added

  autoDisplayUnit is best if added to each helper.
  Here is an example of autoDisplayUnit set to “months” for the first 2 helpers (“6 months” and “1 year”) but not for the 3rd (“2 years”).

  Image Added

• method: this is the "operation" you'd like to operate on the date. The possible values are add, subtract or endOf (1).
  

  Image AddedImage AddedImage Added

  (1) the endOf method needs another property when in use:

  Code Block
  "i18n": "duration.endofyear"

  This will change the text to “end of the year”.

• i18n: is a i18n key that will change the label/text displayed.
  Example:

  Code Block
  { "args": [10,"years"], "method": "add", "i18n": "shared-board.fetching.title" }

  Will have displayed :

  Image Added

  Or, if we change the property to :

  Code Block
  { "args": [10,"years"], "method": "add", "i18n": "foo bar" }

  Image Added