DFS 8.0.2 - 1 Getting started

This chapter introduces the use of DAM for Sitecore. The reader is assumed to have basic Sitecore Editor skills and is assumed to be familiar with Sitecore Editor tools and terms. Parallels are made to how Sitecore Media Library and image fields work.

If unfamiliar with Sitecore specific terms, please read the Sitecore Editors Guide for clarification.

1.1 Assets

DAM for Sitecore is an alternative to Sitecore Media Library. DAM for Sitecore offers a lot of functionality which the standard Sitecore Media Library does not offer. In some areas, they have similar functionality.

The media library is the repository for all images, videos, PDF files, and other files for download that should be shown or be available on the website. Such a media file, is called an asset. It is important to know this as the system underneath DAM for Sitecore is a Digital Asset Management system, or in short a DAM system.

The DAM system is developed to be available in many platforms, not only in Sitecore. You can insert images into Word and PowerPoint, directly from the DAM to. Sitecore Media Library does not offer such integrations into other platforms (e.g. Word). By using a DAM system, everybody within an organization can share the same repository, and work smarter.

1.2 Start using DAM for Sitecore

Every asset in the website descents from the DAM system and the integration of DAM for Sitecore. It is inserted into the webpage by using Sitecore Experience Editor (formerly known as Page Editor) or the Content Editor.

Assets are inserted into either fields, asset fields, or Rich Text fields.

1.2.1 Inserting assets using Rich Text Editor

To insert an asset into a Rich Text field in Sitecore Experience Editor, navigate to a page containing a Rich Text field, and start editing. To insert the asset, click on Insert Assert button in the ribbon.

This will open the Asset Browser, which looks like this:

Any asset known to Sitecore may be inserted in the Rich Text editor. For a list of known asset types, we refer to the Sitecore developer. Furthermore, assets can be made available for download by using the Link to Asset button. Assets with no visual representation will be inserted as a download link (i.e. audio).

However, Digizuite recommends the following:

• Inserting images and videos into Rich Text fields is in general not the recommended way of adding visual elements to the website.
• Inserting images and videos into Rich Text fields is in general not the recommended way of adding visual elements to the website. It becomes more difficult to control the visual identity. Instead, use fields for a specific purpose like the banner image, video for a spot, teaser image, etc.

1.2.2 Inserting assets using Asset fields

Asset fields are fields that may contain any kind of asset: images, videos, pdf files, audio files – anything. When the website shows the selected asset, it will display it accordingly. An image will be displayed as an image, a video as a video and so on.

Some assets can even have more than one representation. A video, for instance, has a thumbnail representation and a video representation. A PDF file may be a thumbnail of the front page or the PDF file. In addition, depending on the implementation of the specific website, different versions of an asset may be shown. The different versions correspond to which quality the asset is displayed in (e.g. resolution of an image).

In the Sitecore Experience Editor, asset fields are similar to standard Sitecore image fields, and they are opened in the small toolbar by clicking on the Choose an image button.

This brings up the Asset Browser.

From which the asset quality is selected.

Note: Depending on the configuration, there may be different qualities.

If an image is selected, then an image is inserted into the asset field in the quality selected.

However, if a video is selected, then a video is inserted:

Note: This is an example of how DAM for Sitecore works out of the box, but it may not be the same thing that happens in any solution. A lot of Sitecore solutions are customized solutions. The Sitecore implementation partner is able to inform about any differences.

1.2.3 Working with the Content Editor

When working in the Sitecore Content Editor, Asset fields are a part of content items. There are previews of the selected assets. Examples of how different asset types behave are shown below:

When clicking on the button 'Browse', the asset browser opens and a list of assets is loaded.

1.3 Three types of asset fields

DAM for Sitecore adds three new field types to Sitecore. There is the Asset field, which is covered in the previous chapter. Furthermore, there are Asset Link fields, which is used for linking to Assets. Lastly, there are Asset Lists, which is used to store multiple assets. The list is flexible and may contain any asset.

1.4 Do not get tempted by Sitecore Media Library

DAM for Sitecore and Sitecore Media Library coexist in Sitecore, and it is possible to use both, but it is strongly recommended to use only DAM for Sitecore. By using Sitecore Media Library, storage is created and only Sitecore Editors can access this. One of the primary objectives for using a DAM is to have a central archive, and by using both libraries the purpose of the DAM is ruined.

There can be a need for using both Sitecore Media Library and DAM for Sitecore in a period of transition to DAM for Sitecore. However, when you complete the transition, you should change to use DAM for Sitecore only.