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 8 Next »

DAM for Sitecore is constructed using pipelines, and it is possible to hook into the pipelines.

Note: Be aware that if you do change the pipelines, you are changing how DAM for Sitecore is supposed to work out of the box, and this may result in undesirable side effects.

The pipelines are defined in the .config files App_Config → Include → damforsitecore → DFS.Pipelines.config

Below are descriptions of the most important pipelines used in the module.

App_Config/Include/damforsitecore/DFS.Pipelines.config

Pipeline

Description

PipelineArgs

DFS.GetAssetFieldValue

This pipeline will return rendering html for an asset item. 

  1. First it will get the html template, determined by the media type and the fieldId (HtmlForAssetType). The html templates are located at:
    Sitecore → System → Modules → Digizuite → MedaDataRoot → AssetTypeOutputRoot.

  2. The different processors will replace the stampvalue in the html template.

  3. The property FieldValue of GetAssetFieldValueArgs will contain the rendering html.


List of processors

  • DFS.Client.Services.Pipelines.GetAssetFieldValue.GetAssetTypeOutput

  • DFS.Client.Services.Pipelines.GetAssetFieldValue.ReplaceTagsWithSelectedValues

  • DFS.Client.Services.Pipelines.GetAssetFieldValue.ReplaceTagsWithAccessValues

  • DFS.Client.Services.Pipelines.GetAssetFieldValue.ReplaceTagsWithConfigValues

  • DFS.Client.Services.Pipelines.GetAssetFieldValue.AppendTagsWithParameterValues

  • DFS.Client.Services.Pipelines.GetAssetFieldValue.ReplaceTagsWithAssetIndexValues

  • DFS.Client.Services.Pipelines.GetAssetFieldValue.RemoveEmptyAttributes

  • DFS.Client.Services.Pipelines.GetAssetFieldValue.SplitFieldValueIntoResult


var renderArgs = new GetAssetFieldValueArgs
{
	AssetItemId = new ID(this.AssetItemId),
	ContextLanguage = Context.Language,
	FieldId = DFS.Fields.HtmlForAssetType.FieldAssetMedia,
	Quality = this.Quality
};


Pipeline

Description

PipelineArgs

DFS.Services.DFSMedia

This pipeline will return the media stream either from the cache or from Digizuite DAM. 

  1. First we check security.

  2. If the media is in the cache we return that.

  3. The media was not in the cache, fetch the media from Digizuite DAM.

  4. We resize the image, if resizing parameters was added.

  5. Store the media in the cache.


List of processors

  • DFS.Client.Services.Pipelines.DFSMedia.SynchronizeAsset (Only In Role: ContentManagement)

  • DFS.Client.Services.Pipelines.DFSMedia.LoadAssetEntity

  • DFS.Client.Services.Pipelines.DFSMedia.GetMediaFromCache

  • DFS.Client.Services.Pipelines.DFSMedia.GetMediaFromDigizuite

  • DFS.Client.Services.Pipelines.DFSMedia.ResizeImage

  • DFS.Client.Services.Pipelines.DFSMedia.SaveToCache

  • DFS.Client.Services.Pipelines.DFSMedia.ResolveFilename


var arguments = new DFSMediaPipelineArgs
{
	Request = mediaRequest,
    Result = new MediaResult()
};



Synchronization

Pipeline

Description

PipelineArgs

DFS.SyncAsset

This pipeline is triggered when you insert Digizuite assets into content fields. 

  1. First it tests if the requested asset is allready synchronized and exists in the asset silo. If the forceUpdate is true, then we skip this check.

  2. Fetch the asset from Digizuite.

  3. Save the asset as /sitecore/media library/Digizuite/Assets.

List of processors

  • DFS.Connect.Pipelines.SyncAsset.ItemExists

  • DFS.Connect.Pipelines.SyncAsset.FetchAsset

  • DFS.Connect.Pipelines.SyncAsset.SaveItem

var arguments = new SyncAssetArgs
{
    AssetId = aid,
    Language = DfsLanguage.GetLanguage(language),
    ForceUpdate = true
};


  • No labels