Magnolia DAM JCR implementation

Edition DX Core





Maven site





  • magnolia-dam-jcr

    • Magnolia specific DAM implementation based on JCR.

    • Stores DAM data in the JCR workspace dam.

    • Provides and configures info.magnolia.dam.jcr.JcrAssetProvider.

  • magnolia-dam-imaging

    • The link between magnolia-dam-jcr and the Imaging module.

    • Provides and configures info.magnolia.dam.imaging.ImagingBasedAssetRenderer, which is info.magnolia.dam.api.AssetRenderer based on magnolia-dam-jcr.

Installing with Maven

Maven is the easiest way to install the module. Add the following to your bundle:

  <version>4.0.0</version> (1)
1 Should you need to specify the module version, do it using <version>.
  <version>4.0.0</version> (1)
1 Should you need to specify the module version, do it using <version>.

Magnolia DAM JCR configuration

As mentioned above, the configuration for info.magnolia.dam.jcr.JcrAssetProvider and info.magnolia.dam.imaging.ImagingBasedAssetRenderer is set by their modules. Finally the configuration looks like this:

Magnolia DAM JCR configuration

NoOpAssetRenderer is configured by the DAM Core module.

Configuring asset download

In the dam.subApps.yaml file within the Resource Files app, you can customize certain properties of the asset download action like the ZIP file name and the maximum size limit when downloading multiple assets.

      icon: icon-download
      availability: *notDeletedAvailability
      icon: icon-download
      zipName: custom_file_name (1)
      maxSizeInBytes: 1024 (2)
        multiple: true
          notDeleted: *notDeleted
1 zipName is an optional property where you assign a default name to the ZIP file. If unset, the batch of assets is downloaded as
2 maxSizeInBytes is an optional property. You can set the maximum size limit of the downloaded ZIP file if needed to improve performance. If this property is not added, there is a 1GB default limit.

Configuring asset upload

You can change the default maximum size limit for uploading assets in the dam.subApps.yaml in the Resource Files app.

      icon: icon-import
      maxSizeInBytes: 104857600 (1)
      availability: *notDeletedWritableRootAvailability
1 Value maxSizeInBytes to suit your requirements.

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.

DAM assets JCR subapp with bytesize column added via definition decoration

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.

      - 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 shown below.

Searching for DAM JCR images

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 Configuration app and update the value of dam-jcrconfignodeNameSearch to the value that you want (e.g., StartWith). The node name search is not indexed and, therefore, a little slower than the full-text search.

DX Core



This widget lets you know where you are on the docs site.

You are currently perusing through the DX Core docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules
6.3 beta

Magnolia 6.3 beta

Magnolia 6.3 is in beta. We are updating docs based on development and feedback. Consider the 6.3 docs currently in a state of progress and not final.

We are working on some 6.3-beta known issues during this phase.