Magnolia DAM JCR implementation
Magnolia specific DAM implementation based on JCR.
Stores DAM data in the JCR workspace
Provides and configures JcrAssetProvider.
The link between
magnolia-dam-jcrand the Imaging module.
Provides and configures ImagingBasedAssetRenderer, which is AssetRenderer based on
Installing with Maven
Maven is the easiest way to install the module. Add the following to your bundle:
<dependency> <groupId>info.magnolia.dam</groupId> <artifactId>magnolia-dam-jcr</artifactId> <version>3.0.23</version> </dependency>
<dependency> <groupId>info.magnolia.dam</groupId> <artifactId>magnolia-dam-imaging</artifactId> <version>3.0.23</version> </dependency>
Magnolia DAM JCR configuration
As mentioned above, the configuration for JcrAssetProvider and ImagingBasedAssetRenderer is set by their modules. Finally the configuration looks like this:
Displaying asset sizes in the asset browser
In the default configuration, asset sizes are not shown in the asset browser since this information is regarded as less important to content editors. However, you can use the definition decoration mechanism to reconfigure the default column composition and add a column that will display the sizes. The sort-by-size function will be also available through the up/down arrows in the column header.
To add the column to the default configuration, create a definition decorator file in your light module, as shown in the example below. Use the YAML
!override directive to specify the position of the column in the column list.
jcrBrowser: workbench: contentViews: - name: tree columns: !override jcrName: &name title: &title jcr:content/size: &size type: java.lang.Long label: Size (bytes)
Searching for DAM JCR assets
Dam assets that are stored in the JCR can be searched for in the
Pages app when adding an image component. An example is depicted below.
The full-text search field, which is marked with a magnifying glass, uses an algorithm that includes the following node name search configurations.
Contains: checks whether the node name contains the search string
StartWith: checks whether the node name starts with the search string
None: ignores LocalName search (only full-text search is used)
To configure the node name search, go to the