DAM
Digital asset management (DAM) Bundled: Community edition Version 6.0.0-beta1 Magnolia 6.4 compatible
About DAM
The DAM module in Magnolia CMS provides the DAM API and its implementation. It is always used with the DAM App, which provides the applications that are built on top of these APIs. For other module dependencies, see the compatibility matrix.
|
DAM 5 and DAM 6 provide almost identical functionality and code. The driving factor for which version to use is the version of Magnolia you’re running.
|
Decoupled asset binary and metadata storage
In DAM module 5.0 and later, Magnolia decouples asset binary and metadata storage, allowing binaries to be stored in AWS S3 while keeping metadata in the dam JCR workspace.
This approach reduces the size of the JCR, speeds up publishing, and enhances search capabilities due to optimized metadata storage.
For S3 configuration information, see the DAM JCR S3 submodule page.
Decoupling metadata and binary storage benefits customers who:
-
Work with many assets or large assets, such as videos or high-resolution images, that don’t fit efficiently in JCR
-
Need to store assets externally in a system that doesn’t support full metadata management
-
Use external storage solutions that are incompatible with the full DAM API
|
Choose a storage method—JCR or an external provider—at deployment time and keep it for your project’s lifecycle. A "hybrid" storage approach isn’t supported; you can’t store some asset binaries in JCR while others are in an external provider. |
The different storage methods don’t impact how authors use assets in the Magnolia AdminCentral UI.
For an overview of DAM features available in Magnolia, see the Digital asset management (DAM) feature page.
See the DAM API for developer-oriented information on extending functionality.