Skip to main content
drupalreleases

Use direct release data with your AI assistant.

Learn more

DAMopen remote

No security coverage Under active development

Connect Drupal to DAMopen to browse and upload shared assets. Keep originals in DAMopen while managing alt text, captions, and crops for each use in Drupal.

DAMopen Remote connects a Drupal 11 site to a shared digital asset library in DAMopen. Editors can find approved images and upload new assets from Drupal’s content editing forms. Originals stay in DAMopen, and Drupal stores local media records and generates the image sizes and crops needed by the site. DAMopen

Features

- Browse and upload from Drupal. Add DAMopen browse and upload widgets to Entity Browser. The optional asset picker supports multiple selection and lets editors enter metadata before uploading. New image uploads are unpublished by default.
- Reuse one image in different contexts. Each selection creates a separate local usage, so a homepage banner and an article can use the same original with different alt text, captions, or crops.
- Control where metadata is saved. Keep field values in Drupal, save them to DAMopen, or save them in both places. Updating an existing DAMopen asset requires an explicit Save in DAMopen action and the appropriate permissions.
- Work with videos and image collections. Optional submodules let editors select or create videos and galleries. Video files stay in DAMopen and play through signed URLs. Each gallery image can have its own local metadata and crop.
- Offer optional AI suggestions. Editors can review suggested image alt text, titles, descriptions, and keywords before applying them.

Post-Installation

1. On the Drupal site that will use the assets, enable DAMopen Remote and go to Configuration → Media → DAMopen connections. Add your DAMopen HTTPS URL and configure the integration account credentials in settings.php.
2. Create a JPEG fallback image style, then go to Configuration → Media → DAMopen mappings and map the remote image resource to a local Drupal media type and image field.
3. Enable an Entity Browser integration submodule and add the DAMopen widgets to the browser used by your content fields. For the DAMopen asset picker, select the mapping and the media form mode that controls which fields editors see.
4. Grant the relevant Drupal and DAMopen permissions. For videos or galleries, enable the optional media integration and configure DAMopen video and gallery mappings.

Additional Requirements

- Drupal 11 with the core Media and Image modules, PHP 8.3 or later, and the ImageMagick 4.x module with the ImageMagick executable. ImageMagick
- A DAMopen instance with JSON:API access over HTTPS and an integration account with the permissions needed for the configured workflows. Uploads require writable JSON:API resources. DAMopen
- The Drupal public file scheme as the default, plus a temporary directory outside the document root for processing originals and staging uploads.
- Some optional collection and shared metadata workflows require companion endpoints installed separately on the DAMopen server.

- Entity Browser 2.16 or later is required for the included Entity Browser widgets. Entity Browser
- Crop API is required for the optional asset picker. Crop API
- AI and AI Image Alt Text, with a vision-capable provider, enable the optional AI suggestions. AI · AI Image Alt Text

Similar projects

- FileField Sources JSON API adds a generic JSON:API source to Drupal file and image fields. DAMopen Remote provides a DAMopen-specific workflow with uploads back to the DAM, Drupal image styles, and independent media usages. FileField Sources JSON API
- Acquia DAM and Bynder connect Drupal to their respective asset platforms. DAMopen Remote connects Drupal to the open-source DAMopen distribution. Acquia DAM · Bynder

Supporting this Module

Use the project’s issue queue to report bugs, suggest improvements, or contribute documentation and patches.

Ask your assistant about DAMopen remote

Check compatibility with your Drupal and PHP version, maintenance and security coverage, from current release data. How it works

Depends on

Dependencies of the latest stable release

No dependencies recorded for this project.

Required by

Tracked projects that depend on this one

No tracked projects depend on this one yet.

Activity

Tracked releases
2
Tracked since
Nov 2026
Latest release
1 hour ago
Releases (12 mo)
2 ▲ from 0
Maintenance
Active

Releases

Version Type Core PHP Release date
1.0.x-dev Dev 11 PHP ^8.3 Nov 18, 2026
1.x-dev Dev 11 PHP ^8.3 Nov 18, 2026