OpenText DAM (OTMM) - Drupal Integration and Automation

Common Integration Use Cases Between OpenText DAM (OTMM) and Drupal

1. Centralized product image delivery to Drupal product and catalog pages

Data flow: OpenText DAM (OTMM) to Drupal

OTMM can serve as the master repository for approved product images, while Drupal pulls the correct renditions, metadata, and usage rights into product detail pages, category pages, and landing pages. This ensures web teams always publish the latest approved assets without manually downloading and re-uploading files.

• Improves consistency across product pages and microsites
• Reduces duplicate asset storage in Drupal
• Speeds up campaign launches and product updates

2. Automated publishing of campaign assets to marketing microsites

Data flow: OpenText DAM (OTMM) to Drupal

Marketing teams can store campaign banners, hero images, videos, and social cutdowns in OTMM and expose selected assets to Drupal for use on campaign microsites, landing pages, and promotional content hubs. Drupal editors can search by campaign, region, or approval status and insert approved assets directly into pages.

• Supports faster campaign execution across multiple web properties
• Ensures only approved assets are published
• Enables reuse of campaign content across channels

3. Metadata synchronization for better content discovery and governance

Data flow: Bi-directional

OTMM asset metadata such as product category, campaign name, usage rights, expiration date, language, and region can be synchronized with Drupal taxonomy and content fields. In return, Drupal content context such as page type, audience segment, or site location can be written back to OTMM for reporting and governance.

• Improves search and filtering for editors in both systems
• Supports compliance with usage rights and expiration rules
• Creates a shared content language across marketing and web teams

4. Museum and heritage collection storytelling with rich media

Data flow: OpenText DAM (OTMM) to Drupal

Museums and heritage organizations can use OTMM to manage high-resolution photos, archival video, and exhibit media, then publish selected assets into Drupal exhibit pages, digital collections, and educational portals. Drupal can combine the media with structured interpretive content, timelines, and taxonomy-driven browsing.

• Supports high-quality digital exhibitions and online collections
• Preserves master assets in a controlled DAM environment
• Improves visitor engagement through curated media experiences

5. Multi-site content reuse for regional and brand websites

Data flow: OpenText DAM (OTMM) to Drupal

Enterprises running multiple Drupal sites can use OTMM as the shared source for approved images and videos across regions, brands, or business units. Each Drupal site can reference the same asset while applying local metadata, translations, or page-specific cropping rules.

• Eliminates asset duplication across sites
• Maintains brand consistency globally
• Reduces localization and content maintenance effort

6. Rights-managed media publishing with expiration control

Data flow: OpenText DAM (OTMM) to Drupal

OTMM can manage licensing, expiration dates, and usage restrictions for third-party or time-bound media. Drupal can display only assets that are currently approved for web use and automatically hide or replace expired content based on DAM status.

• Reduces legal and compliance risk
• Prevents expired campaign or licensed media from remaining live
• Supports controlled publishing for regulated industries

7. Video asset delivery for editorial and on-demand experiences

Data flow: OpenText DAM (OTMM) to Drupal

Broadcast, event, and marketing video assets stored in OTMM can be embedded into Drupal editorial pages, newsrooms, event recaps, and on-demand content hubs. Drupal can consume the correct video format, thumbnail, and caption metadata from OTMM to create a consistent playback experience.

• Improves performance by serving optimized video renditions
• Supports editorial teams with easy video reuse
• Enhances audience engagement on content-rich sites

8. Editorial asset request and approval workflow

Data flow: Drupal to OpenText DAM (OTMM), then OpenText DAM (OTMM) to Drupal

Drupal editors can request assets from OTMM through a content workflow, such as selecting a placeholder image or requesting a missing product photo. Once the asset is approved and added to OTMM, it becomes available back in Drupal for publishing. This creates a controlled handoff between content teams and asset managers.

• Streamlines collaboration between web editors and DAM administrators
• Reduces delays caused by manual email-based asset requests
• Improves publishing quality and governance