Gravatar for

Question by Deepa, Oct 15, 2018 6:27 PM

What is the Coveo source for Digizuite DAM contents

@Jean-François L'Heureux We have a project that has a need for searching content on digital assets. So we are going to use Digizuite DAM as our digital asset management with Sitecore. We will be syncing the assets in DAM with Sitecore but the items will not be created physically in Sitecore. It will instead create a pointer back to the DAM. DAM has all the contents and that is the data that has to be searched. During our training we went through Web Source to index items from helix website, Is there an existing source that I can use for the above requirement, if not what could be the best approach on this?

1 Reply
Gravatar for

Answer by Jean-François L'Heureux, Oct 15, 2018 6:40 PM


I have never tried integrating Digizuite DAM and Coveo for Sitecore. but it should be very easy.

As Digizuite DAM synchronizes the media assets as Sitecore items, there is no need to use another Coveo connector. Just use Coveo for Sitecore and index the folder where the DAM assets are synchronized (using a crawler root). Coveo for Sitecore uses Sitecore APIs to get the media files so it does not matter if the media files are stored in a database blob, the file system, or a remote system. If Digizuite DAM integrates with the same APIs, it will work very well with Coveo for Sitecore.

That being said, I recommend you create some custom inbound filter processors to only index the media files you want to be displayed as distinct search results (e.g.: PDF documents). It does not make sense to index every image and asset from the DAM if you are not returning them in the search results.

Gravatar for

Comment by twellstx, Jan 14, 2019 7:23 PM

@Jean-François L'Heureux, Digizuite works well with Coveo, but we are running into a problem. Digizuite just stores meta data in Sitecore and not the actual media in a blob. This is not a problem to use the coveoPostItemProcessingPipeline and set the BinaryData. In fact everything is working great except for Audio files.

For Video and Audio files we need to set the binary data as the description/transcript and not the actual video or audio file. This works for video, but audio are being treated as audio files and not text but some pipeline (utilizing the same code as video). There seems to be a Coveo pipeline that sees the item as an audio media item no matter how programmatically it is set. I can move the asset out of from under the media library into the site content and it is indexed as a text file as expected, but when it is in the media library Coveo treats it as an audio file and will not allow the coveoPostItemProcessingPipeline to overwrite the item data.

How can this behavior be overwritten?

Ask a question