...
In order for the above property mapping to work, it is important to ensure that Digizuite also sends the specific metadata field to the Episerver integration - and that it's named the same was as specified in the attribute. This is done by customizing the output parameters for the "GetEpiserverAssets" search in the DAM Center, and adding the requested field as an output parameter, while ensuring it's named correctly.
You can read more about adding custom input and output parameters here: https://digizuite.atlassian.net/wiki/spaces/DD/pages/799604821/DFE+1.0.0+-+6+Customizing+input+and+output+metadata
...
| Code Block | ||
|---|---|---|
| ||
[DigizuiteMediaFormat("Small"imageSmall", "3C95F58F-5DD7-4AFB-B1C8-48E05901CE6D")] [ScaffoldColumn(false)] public virtual Blob Small { get; set; } |
This can simply be achieved by assigning the DigizuiteMediaFormat attribute to a Blob property in Episerver. The attribute should either contain part of the name of the media format, or the media format IDYou have to apply the json id and the guid of the mediaformat. This requires that the mediaformat has been added to the output parameters for the "GetEpiserverAssets" search in the DAM Center.
A cool benefit of this is that by assigning a blob, due to Episervers convention, you'll also get a pretty url pointing directly to that media format, like this: "/globalassets/digizuite/155-las-vegas.JPG/small" and we ensure the correct mimetype when requesting the asset.
Read more about Asset URL's here: https://digizuite.atlassian.net/wiki/spaces/DD/pages/799768707/DFE+1.0.0+-+8+Customizing+Asset+Urls
...