Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

 

Part of the new DAM 4.5.1 release is represented by the support offered for the new DAM for Sitecore module. The 2 main changes are:

  • Support in the installer to choose between DAM For Sitecore 4 and DAM for Sitecore 5
  • Default previews

How to access/use the new implementation?

For the time being, these changes are disabled, therefore you will not be able to see or react on them.

When starting the installer a drop-down menu will be visible which will enable you to select one of the following values:

  • Empty - do not install any of the DAM for Sitecore modules
  • DAM for Sitecore 4 - which will install DAM for Sitecore module 4

  • DAM for Sitecore 5 - which will install DAM for Sitecore module 5

If you have chosen to install DAM for Sitecore 5, the installer will automatically import the default previews assets to the catalog folder Default previews. It will also add the required configuration to the Config Manager in DAM for Sitecore → Config → Default previews. The import process will create upload jobs for the assets, but will not wait for them to finish. This means that when you log in to the DAM Center after upgrading/installing, you may see that some jobs are running. The default previews will work when these jobs have finished.

Default previews

The default preview feature is used through the asset-streamer. The point of this feature is to have the asset-streamer deliver another media file, if the requested file was not found, so the user does not get 404 file not found.
You configure this in the config manager under the tab "Default previews".

How the new implementation works?

Default previews

 In this example we request a thumb of an asset which is of the type excel. Is has no thumb to return and returns 404 - File or directory not found.
/dmm3bwsv3/27_3_11_9_11_0_fdeb8e2f-4fa8-4f96-a394-3e6d6db53ebb_False.jpg?mptdid=0

If we then assume the configuration for the default preview is made and then call the same url again.
/dmm3bwsv3/27_3_11_9_11_0_fdeb8e2f-4fa8-4f96-a394-3e6d6db53ebb_False.jpg?mptdid=0

Now it should return an substitute image. See the next section on how to configure this.

How to configure the new implementation?

CreatedADGroupsAndUsers

CreatedADGroupsAndUsers have moved.

It now resides in the dam center .zip file. From version 4.5.1 you will find it here:

4.5.1\4.5.1.zip\CreateADGroupsAndUsers

 

Default previews

To configure the default previews, there are 4 steps to go through:

  1. Upload the substitute assets to the catalog folder called Default preview icons. It is important that you place them there, because there is a workflow (AssetSyncFolder) that automatically publishes to the channel folder Default preview icons.
  2. Create the formats you want your substitute assets to be transcoded into and then create a profile with these formats.
  3. Add this profile to Profiles and destinations in config manager. Only add this one time pointing to the channel folder Default preview icons. We recommend that you add this to the relevant version.
  4. Go to the config version where you want to enable the default preview feature. In the screenshot you can see that we have configured it for Dam For Sitecore version 5.0.0.



    Note: The Default previews is an iterative metagroup. The group consists of 4 fields:
     
    Assettype (required)
    The assettype you want a substitute for.

    Preview Asset (required)
    The asset you want as the subsitute.
     
    Input Mediaformat
    Select the mediaformat that this substitute should match up against.

    Output Mediaformat
    Select the mediaformat that the selected substitute asset should be returned in.

    The assetstreamer logic when default preview is configured
    If the requested assetId and mediaformatId did not return any content, then we go into the default preview logic.
    a) Get default configuration for the version bound in the accesskey. If empty, it fall back to the dam center version to see if it has any configuration.
    b) Test if there is any configuration for the requested assettype.
    c) We then test if there is any configuration where Input mediaformat equals the requested mediaformat and the output mediaformat is set. Then we try to stream that format for the configured preview asset.
    d) If c did not find anything, then we find the first configuration, where input mediaformat equals 0 and streams that with the requested mediaformat or the output mediaformat if defined.
    e) return 404 if none of the above was a success.

  5. On the config version you just added the default previews to, you have to set the config param Default Preview Destination to the destination where the substitute assets are published to. Most of the time this will be FrontenData SM.

Adaptive Bitrate

A new video quality has been added to the DamCenter: "Adaptive Bitrate HQ"

How to Add the format
  • Go to System Tools / Profiles
  • Select the profile "Digizuite™ Video Portal Videos"
  • Select "Adaptive Bitrate HQ" in the "Format qualities" drop down.
  • Click the "+" icon
  • Click Save.

See Video Portal Installation & Configuration guide, for instructions regarding the ConfigManager configuration.

How to remove the format
  • Go to System tools / Profiles.
  • Select the "Digizuite™ Video Portal Videos" profile
  • Select the "Adaptive Bitrate HQ" in the format qualities list.
  • Click on the "-" icon
  • Click Save

Requirements

Batch System version 2.4.21 or newer

Warning

If the Adaptive Bitrate feature is not used, the "Adaptive Bitrate HQ" quality should be deselected, as it places a high load on the transcode system.

What has been released?

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

What is in the next release?

The next release it will contain bug fixes.

 

 

 

 

  • No labels