Dynamic Media with OpenAPI capabilities frequently asked questions
CREATED FOR:
- User
AVAILABILITYThe status of an asset in Experience Manager Assets is governed by jcr:content/metadata/dam:status property. The values of this property can be:
-
Approved
-
Rejected
-
Changes requested
Experience Manager Assets distinguishes Approved status using an approved icon available on the asset card, as depicted in the following images for Admin and Asset views:
Admin view
Assets view
To approve all assets in a folder, see instructions on how to bulk approve assets in a folder. There is also a video that depicts the entire process.
After setting up a folder for bulk approval, all new assets that are added to the folder are approved automatically. All existing assets are approved after reprocessing assets. See Reprocessing digital assets for instructions on how to reprocess assets. If you copy or move unapproved assets from any other folder, you need to reprocess the assets.
The asset is marked as Rejected, if the administrator specifies Rejected or Changes requested values. Experience Manager Assets distinguishes the Rejected status using
Similarly, Experience Manager Assets distinguishes the Rejected status in Assets view using the following Rejected status on the asset card:
Yes, you can approve multiple assets within a folder simultaneously.
Execute the following steps to approve multiple assets simultaneously in Experience Manager Assets Admin view:
- Select the asset(s) and click Properties.
- In the Basic tab, scroll down to Review Status.
- Change the review status to Approved.
- Click Save & Close.
Similarly, to approve multiple assets simultaneously within a folder in Assets view:
-
Select the asset(s) and click Bulk Metadata Edit.
-
Select Approved in the Status field available in the Properties section in the right pane.
-
Click Save.
Central asset governance in Experience Manager allows the DAM Administrators or Brand Managers to manage access to assets. They can restrict the access by configuring roles or by setting activation and deactivation time for approved assets on the authoring side, specifically on the AEM as a Cloud Service author instance.
End-users searching or utilizing delivery URLs can gain access to restricted assets upon successfully passing the authorization process.
For more information, see Restrict access to assets in Experience Manager.
Dynamic Media with OpenAPI capabilities and Dynamic Media represent distinct solutions, each offering its specialized delivery capabilities. It is imperative to thoroughly review your specific requirements to determine the most fitting solution that aligns with your needs.
General guidance from Adobe is to leverage Dynamic Media with OpenAPI stack for any integration use cases (1st or 3rd party apps). If there already exists an integration with Dynamic Media stack, recommendation is to not change it as OpenAPI stack URLs are different in structure. Only for any net new integration use cases, leverage OpenAPI stack. If your use case requires advanced modifiers not available with OpenAPI stack, then avoid the OpenAPI stack until Adobe bridges the gap. Even for basic native delivery from AEM Assets Cloud Services, OpenAPI stack can be evaluated as long as your use case is covered with the modifiers available with OpenAPI stack. In conclusion, Dynamic Media and Dynamic Media with OpenAPI stack can co-exist, depending on the nature of your use case.
The following are some of the key differences between Dynamic Media with OpenAPI capabilities and Dynamic Media:
The table below outlines the key differences between the two solutions: