DAM Module App

Introduction

The DAM module app is split into 6 sub modules

• dam-api
  Assets interfaces definitions
  Provider registry
• dam-jcr
  JCR implementation of the Asset API's
• dam-app
  M5.2 JCR Asset App definition & specific implementations (Actions, views, ...)
  Also include the new Asset App definition and AssetProviderContainer definition
• dam-templating
  Expose Assets and Asset operations used in the templating part (Model, Pages, ....)
• dam-core
  Core functions like Uri to Repository mapping or download servlet
• dam-compatibility
  Expose the old implementation in order to enforce the compatibility betweem DAM module1.2.x and 2.x

Module hierarchy:

dam-api

API Proposal:

API Components:

Provider & Provider registry

exposes

configuration

implementation

Item / Asset / AssetFolder / AssetKey

Rendition

(link)? how to

Metadata

ProviderRegistry

MediaType

A MediaType is defined based on the asset mimeType and can be see as a grouping of mimeTypes.
MediaType are used in:

• Providers, in order to
  
  • define the supported provider's mediaType (A provider may only support videos, or both images and documents).
• Asset content App to define available actions on an Asset element
  
  • Display a preview icon for mediaType image and use the following preview component
• Asset provider container
  • Filter views (Tree view) based on a desired mediaType (Only display images or videos)

configuration

dam-app

M5.2.x configuration.

dam-jcr

AbstractAssetProvider has getter/setter for supported MediaTypes. These supported MediaTypes are defined in the config node of the provider module. 

dam-jcr

dam-app

Asset provider container

implemetation

The Asset provider container should implements:

• Container.Filterable
• Container.Hierarchical 
• Container.Sortable
• Container.Indexed

Input arguments are:

• AssetProvider specific implementation
• AssetProviderContainer configuration
  
  • Root path
  • ...