OpenText DAM (OTMM) - inriver Integration and Automation

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

OpenText DAM (OTMM) and inriver complement each other well in organizations that need strong product content governance and rich digital asset management. inriver serves as the system of record for product information, while OTMM manages the approved images, videos, and campaign assets that support product storytelling and channel delivery. Together, they help teams publish complete, consistent, and localized product experiences across commerce, print, partner, and marketing channels.

1. Product Asset Linking from OTMM to inriver

Use OTMM as the central repository for approved product images, videos, and supporting media, then sync asset references and metadata into inriver so product managers can attach the right assets to SKUs, variants, and product families.

• Direction: OpenText DAM (OTMM) to inriver
• Business value: Faster product enrichment and fewer manual file uploads
• Typical workflow: DAM curates approved assets, inriver receives asset URLs, renditions, usage rights, and metadata for product association

2. New Product Launch Content Assembly

When a new product is created in inriver, the platform can trigger a request for required images, lifestyle shots, and demo videos from OTMM. Product teams can then complete launch-ready product records with approved digital assets before publishing to channels.

• Direction: Bi-directional, with inriver initiating requests and OTMM supplying assets
• Business value: Shorter launch cycles and better launch completeness
• Typical workflow: inriver identifies missing media, OTMM provides approved assets, inriver publishes enriched product content

3. Automated Asset Approval and Publishing Governance

Marketing and creative teams can manage asset approval in OTMM, while inriver only receives assets that meet defined business rules such as approved status, language, region, usage rights, and expiration date. This prevents unapproved or outdated media from being used in product content.

• Direction: OpenText DAM (OTMM) to inriver
• Business value: Reduced compliance risk and stronger brand control
• Typical workflow: OTMM approval status changes trigger asset availability in inriver for product publishing

4. Localization of Product Content with Region-Specific Assets

For global markets, inriver can manage localized product descriptions and channel-specific product data, while OTMM supplies region-specific images, translated packaging visuals, and localized campaign videos. This ensures each market receives the correct combination of product copy and media.

• Direction: Bi-directional
• Business value: Better market relevance and fewer localization errors
• Typical workflow: inriver determines market requirements, OTMM provides localized renditions and language-specific assets, inriver publishes market-ready product pages

5. Channel-Specific Asset Distribution for Commerce and Partner Portals

inriver can determine which product assets are needed for each channel, such as e-commerce, distributor portals, print catalogs, or mobile apps. OTMM then delivers the correct renditions and formats, such as high-resolution images for print or compressed videos for mobile.

• Direction: inriver to OpenText DAM (OTMM) and OpenText DAM (OTMM) to inriver
• Business value: Consistent product presentation across channels with less manual reformatting
• Typical workflow: inriver defines channel rules, OTMM generates and stores renditions, inriver publishes channel-ready content

6. Campaign Asset Reuse for Product Storytelling

Marketing teams often create campaign images, banners, and videos in OTMM that can also support product storytelling in inriver. By integrating the systems, approved campaign assets can be reused in product detail pages, landing pages, and seasonal promotions without duplicate asset management.

• Direction: OpenText DAM (OTMM) to inriver
• Business value: Better asset reuse and stronger alignment between marketing and product teams
• Typical workflow: OTMM stores campaign assets, inriver links them to relevant products and promotions

7. Museum and Heritage Collection Content Enrichment

For museums and heritage organizations, OTMM can manage digital photos and videos of collections, exhibitions, and events, while inriver can structure the associated item information, provenance details, and public-facing descriptions. This supports consistent publishing across websites, digital catalogs, and educational portals.

• Direction: OpenText DAM (OTMM) to inriver
• Business value: Improved content consistency and easier public access to collection information
• Typical workflow: OTMM stores collection media, inriver manages item metadata and publishes enriched records to digital channels

8. Asset Expiration and Product Content Cleanup

OTMM can track asset rights, expiration dates, and usage restrictions, then notify inriver when an image or video is no longer valid for use. inriver can automatically remove or flag the asset from product records to prevent expired or non-compliant content from being published.

• Direction: OpenText DAM (OTMM) to inriver
• Business value: Lower legal and brand risk and reduced manual cleanup effort
• Typical workflow: OTMM monitors asset validity, inriver updates product associations when assets expire

These integrations are most effective when inriver remains the master for product data and OTMM remains the master for approved digital assets. That separation of responsibilities helps teams work faster while maintaining governance, consistency, and channel readiness.