Salta al contenuto principale
Servizi

AEM Assets and Dynamic Media: a governed DAM and assets in delivery

Metadata model, folder structure, processing and delivery with Dynamic Media, to turn the DAM into a reliable service for brand and product teams.

AEM Assets is rarely a technology problem and almost always a modeling problem. A DAM that grows without a taxonomy, without metadata rules and without clear roles becomes a shared folder with a nicer interface: assets are hard to find, they get duplicated, usage rights are not tracked and delivery depends on manual procedures. Our AEM Assets consulting therefore starts from the model and moves to the technology, not the other way around.

We work on the design of folder structure, metadata schemas, processing profiles and integration with AEM Sites, and on asset delivery through Dynamic Media, the component based on Scene7 technology. The goal is that people producing content find what they need, those publishing it always use the right version, and those managing delivery do not have to create variants of every image by hand.

On this page we describe the topics we handle most often: DAM governance, processing on AEM as a Cloud Service with Asset Compute, delivery through Dynamic Media, migration of existing libraries and integration with Sites. Available features depend on license and program configuration, and should be verified case by case [VERIFICARE].

Metadata model, taxonomy and folder structure

The first intervention on a DAM is almost always the information model. Together with brand, product and legal teams we define which metadata are mandatory, which optional, which controlled by vocabularies and which inherited from folders. Metadata schemas in AEM Assets allow fields to be differentiated by asset type, and a good schema reduces upload errors and improves search quality.

Folder structure should follow a stable logic, for example by brand, market or channel, avoiding hierarchies that mirror the org chart and change with every reorganization. We define group permissions, naming rules and approval processes, and evaluate where tags and collections are preferable to duplication. Where assisted tagging features are used, we verify their results before relying on them [VERIFICARE].

Asset processing and Asset Compute

On AEM as a Cloud Service asset processing relies on managed microservices, with direct binary upload to cloud storage and configurable processing profiles. This largely replaces the DAM Update Asset workflows of the on-premise version, which often contain custom steps that need rewriting. A central aspect of an assessment on Assets is precisely understanding which customizations exist and which can be replaced by standard configuration.

Where standard configuration is not enough, custom workers can be developed with Asset Compute for specific operations such as particular renditions, metadata extraction or integrations with external services. Before developing, we always evaluate whether the need is truly specific: every custom worker is code to maintain, test and update along with the platform.

Dynamic Media and Scene7: delivery and optimization

Dynamic Media makes it possible to publish images, video and interactive content by generating variants on demand through parameterized URLs and presets, with delivery through a CDN. For a multi-market site with many formats, this reduces manual work on renditions and centralizes management of crops, sizes and quality. Well-designed image presets, image sets, 360-degree spin sets and configured viewers work well.

Introducing Dynamic Media does require conscious decisions: how Dynamic Media URLs and DAM paths coexist, how image SEO and alt text are handled, how an updated asset is invalidated, how the component is integrated into the site. We design these choices together with the front-end team and verify the impact on LCP, as described on the page about performance, Dispatcher and CDN. License options should be verified with Adobe [VERIFICARE].

Migration and integration with AEM Sites

Migrating an existing asset library to AEM Assets is a data project before it is a technology one. It needs an inventory, deduplication, metadata mapping from source systems, rules for assets without information, and a batched loading plan with checks. In the context of an AEM as a Cloud Service migration, the Content Transfer Tool also transfers assets, but it pays to clean up first: loading fifty thousand useless assets costs the same as loading useful ones.

Integration with AEM Sites concerns the components that reference assets, the behavior of public paths, handling of rights and expiry, and propagation of updates. We verify that components use suitable renditions, that adaptive images do not download oversized versions, and that replacing an asset is correctly reflected on pages and caches. Where integrations with PIM or brand management systems are required, we design them as separate, testable services.

Governance, roles and adoption

A DAM works if people use it as intended. For this reason our work includes the definition of roles and permissions, training of key users and a short set of guidelines written for those who upload assets every day. Overly rigid governance pushes people to share files outside the system, while overly permissive governance reproduces the initial disorder.

We also define DAM health indicators: percentage of assets with complete mandatory metadata, unreferenced assets, duplicates, processing times. These are simple measures that show whether the model holds over time. Reference values depend on the client's context and should be set together with them.

FAQ

AEM Assets and Dynamic Media FAQ

No. AEM Assets is the DAM where assets are uploaded, organized and governed. Dynamic Media is the Scene7-based delivery component that generates variants on demand and distributes them through a CDN. They can be used together, but they require specific configuration and licensing [VERIFICARE].

By starting from an inventory of the fields actually in use, defining with the teams which are mandatory and which are controlled by vocabularies, and planning a migration of existing values. We proceed by asset type, not all at once, to reduce risk.

Direct binary upload, processing through microservices and configurable profiles change, along with the need to rewrite custom workflows. Which customizations are still needed must be verified case by case.

Yes, but the project always starts with inventory and data cleanup. We define metadata mapping, rules for incomplete assets and a batched loading plan with checks. Timelines depend on volumes and the quality of source data.

It can, if presets are well designed and components request appropriate sizes. It is not automatic: the effect on LCP and page weight must be measured, and cache and invalidation of updated assets must be handled carefully.

Bring order to your AEM DAM

Tell us about volumes, source systems and search or delivery problems. We will propose a scope for metadata model, processing and Dynamic Media.

Request AEM Assets consulting