Home | Connectors | OpenText DAM (OTMM) | OpenText DAM (OTMM) - Consonance Integration and Automation

OpenText DAM (OTMM) - Consonance Integration and Automation

Integrate OpenText DAM (OTMM) Digital Asset Management (DAM) and Consonance Marketing apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

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

OpenText DAM (OTMM) and Consonance complement each other well in publishing environments where title metadata, editorial workflows, and rights management must stay aligned with approved visual and media assets. OTMM provides centralized control over images, video, and marketing assets, while Consonance manages the publishing lifecycle, title metadata, production schedules, and rights workflows. Integrating the two platforms helps publishers reduce manual asset handling, improve metadata accuracy, and accelerate multi-channel publication.

1. Link approved cover art and jacket images to title records

Data flow: OpenText DAM (OTMM) to Consonance

When cover designs, jacket images, spine artwork, or author photos are approved in OTMM, the assets can be automatically linked to the corresponding title record in Consonance. This ensures editorial, production, and sales teams always work from the latest approved visual assets.

  • Reduces the risk of using outdated or unapproved cover files
  • Speeds up title setup and production handoff
  • Supports consistent presentation across print, ebook, and retail channels

2. Synchronize marketing assets for launch campaigns

Data flow: OpenText DAM (OTMM) to Consonance

Marketing teams often store launch banners, social media graphics, author headshots, and promotional videos in OTMM. Integration can push approved campaign assets into Consonance title workflows so launch teams can access the right materials during publication planning and release coordination.

  • Improves coordination between marketing and publishing operations
  • Ensures campaign assets are tied to the correct publication date and title
  • Reduces time spent searching for launch-ready files across systems

3. Publish metadata-driven asset requests from Consonance to DAM

Data flow: Consonance to OpenText DAM (OTMM)

As new titles move through acquisition and editorial stages in Consonance, the system can trigger asset requests in OTMM for missing items such as cover concepts, author portraits, or promotional video clips. Asset teams receive structured requests based on title metadata, format, imprint, and release schedule.

  • Creates a more controlled and traceable asset intake process
  • Aligns creative production with publishing milestones
  • Helps prevent delays caused by missing media dependencies

4. Maintain rights and usage restrictions for media assets

Data flow: Bi-directional

Consonance manages rights and publishing permissions for titles, while OTMM can store usage rights, expiration dates, and territory restrictions for associated images and videos. A bi-directional integration keeps rights information synchronized so only approved assets are used in specific editions, regions, or channels.

  • Supports compliance with licensing and territorial restrictions
  • Reduces legal and contractual risk
  • Prevents accidental reuse of expired or restricted media

5. Deliver final production assets to downstream distribution workflows

Data flow: OpenText DAM (OTMM) to Consonance

Once final cover files, interior illustrations, or audio and video supplements are approved in OTMM, they can be delivered to Consonance for inclusion in print, digital, and audio production packages. Consonance can then coordinate the release of those assets to printers, ebook vendors, and distribution partners.

  • Improves production readiness for multi-format publishing
  • Reduces manual file transfer and version confusion
  • Supports faster handoff to external production vendors

6. Centralize title-linked media for sales and retail channels

Data flow: Bi-directional

Consonance holds authoritative title metadata, while OTMM stores the approved media assets that support retail and sales enablement. Integration can keep title identifiers, ISBNs, imprint data, and asset references aligned so sales teams and channel partners can access the correct cover images, author bios, and promotional content.

  • Improves metadata consistency across internal and external systems
  • Supports accurate syndication to retailers and industry databases
  • Reduces rework caused by mismatched title and asset records

7. Support audit-ready publishing and asset governance

Data flow: Bi-directional

For publishers with strict governance requirements, integration can create an audit trail between title workflow events in Consonance and asset approvals in OTMM. This provides visibility into who approved which asset, when it was linked to a title, and which version was used in production.

  • Strengthens editorial and production accountability
  • Helps with compliance and internal audit requirements
  • Makes it easier to resolve disputes over asset versioning or approval status

8. Improve launch readiness reporting across title and asset workflows

Data flow: Consonance to OpenText DAM (OTMM), with reporting back to Consonance

Consonance can track title milestones such as manuscript approval, design completion, and publication date, while OTMM can report whether required assets are available, approved, and correctly tagged. Together, the systems provide a more complete view of launch readiness for production and marketing teams.

  • Identifies missing assets before publication deadlines
  • Improves cross-functional planning between editorial, design, and marketing
  • Helps management monitor bottlenecks across the publishing pipeline

In summary, integrating OpenText DAM (OTMM) with Consonance creates a controlled flow between title metadata and approved media assets. The result is better collaboration across editorial, production, rights, and marketing teams, with fewer manual steps and stronger governance over publishing content.

How to integrate and automate OpenText DAM (OTMM) with Consonance using OneTeg?