This document provides answers to common questions about the integration and management of assets between Acquia DAM and Drupal.

General¶

• Do users have the same permissions to assets in the module as in DAM?
  Yes, users authenticate into DAM first, so permissions match. Check the user’s role permissions if they do not see the correct assets.

• Why do the new features appear in the updated Acquia DAM module instead of another version of the existing Media Acquia DAM module?
  The existing Media Acquia DAM module connects to the Acquia DAM Classic or WebDAM. To enhance and expand the module for specific DAM use cases and improve documentation, the updated Acquia DAM module provides a more efficient solution. This approach allows for better scalability and iteration of new features.

• The media_acquiadam module requires users to authenticate with their DAM credentials so their DAM role and permissions are honored in Drupal. Does the same apply?
  Yes, users authenticate with their DAM credentials.

• Can archived assets be accessed using the Acquia DAM module?
  No, the Drupal module does not return archived assets in its search.

Asset and metadata updates¶

• What happens when assets are updated in the Acquia DAM system?
  Assets updated in the Acquia DAM system will automatically be reflected through the cron job. Additionally, editors have the option to manually run the Check for update option within the Drupal application under the DAM media listing to ensure the updated assets are quickly reflected in Drupal.

• What happens if assets are not updated in the Drupal application after changes are made to the finalized version in the Acquia DAM system?
  Yes, even if the cron job runs, the assets will not automatically update in the Drupal application when the finalized version is changed in the Acquia DAM system. Editors must manually use the Check for update option within the DAM media listing in Drupal to ensure the updated assets are promptly reflected in the application.

• What happens when assets metadata are updated in the Acquia DAM system?
  Editors can also manually run the Sync metadata option within the DAM media listing in Drupal to ensure the updated metadata is promptly reflected.

• Does the syncing only work one way from DAM to Drupal?
  Yes, syncing works one way from DAM to Drupal.

Asset management and deletion¶

• What happens if assets expire, are unreleased, or deleted in the Acquia DAM system?
  The cron job automatically handles these changes by setting the status of the assets to Unpublished in the Drupal application.

• What happens if assets are deleted in the Drupal application?
  Deleting assets from a Drupal application is not recommended. If this action is taken intentionally, it disrupts the sync process, as the deleted assets cannot be restored. Consequently, the customer must reattach the assets to the content manually.

Media sources and asset serving¶

• Can I extend the media sources of supported asset types?
  Currently, the supported asset types in Acquia DAM include Audio, Documents, Generic, Image, PDF, Spinset, and Video. There is also an option to create your own media types if you want to extend your search options.

• How can I serve assets through my web application domain instead of the DAM CDN?
  By enabling the Download and sync assets option, assets are served through your web application domain.

Bulk import and asset management¶

• Can I import assets from all categories with a single click?
  No, the administrator must add individual categories in order to import assets from each category.

• Can I import assets that do not belong to any category?
  No, only assets that belong to a specific category can be imported.

• Does clicking Save import all assets immediately?
  No, when you click the save button, it only saves the configuration for asset import for specific categories and media types. The cron job then processes the configuration and imports the assets in batches.

• If new assets are added to the Acquia DAM System, do I need to resave the configuration to import them?
  No, the configuration is saved once, and the cron job automatically picks up the saved configuration. The cron job imports newly added assets without the need to resave the configuration.

• What happens if asset categories are removed?
  The cron job only imports assets that belong to the saved configurations. Any removed categories are not considered for asset import in the scheduled cron job.

• Why do I not see all the assets imported into the Drupal file system after the cron job finishes?
  The cron job imports assets in batches, so it is possible that not all assets were processed in the current run. The remaining assets are imported during the next scheduled cron job. If you need to import the assets sooner, you can manually trigger the cron job.

For more related articles, visit:

• How do I use the Acquia DAM module?
• How do I use the Bulk Import feature?
• How to migrate from Media Acquia module to Acquia DAM module?
• What is the difference between the latest Acquia DAM module and the Media: Acquia DAM module?