Consonance - OpenText Extended ECM Platform Integration and Automation

Common Integration Use Cases Between Consonance and OpenText Extended ECM Platform

1. Centralized manuscript and title document repository

Data flow: Consonance ? OpenText Extended ECM Platform

Publishers can automatically store manuscript files, author agreements, editorial markups, cover concepts, and production-ready assets from Consonance into OpenText Extended ECM Platform as the controlled system of record. This gives editorial, legal, production, and compliance teams a single governed repository for all title-related documents, with version control, retention rules, and audit trails.

• Reduces duplicate file storage across shared drives and email
• Improves document retrieval for editorial and production teams
• Supports governance for contracts, approvals, and final deliverables

2. Rights and contract document management

Data flow: Bi-directional

Consonance can pass rights metadata, territory details, and title associations to OpenText Extended ECM Platform, while OpenText stores the signed contracts, amendments, and supporting legal documents. Rights managers can access the latest contractual evidence directly from the publishing workflow, while legal teams can update contract status and document versions in the ECM environment.

• Improves visibility into rights availability by territory and format
• Speeds up contract review and renewal workflows
• Creates a defensible audit trail for licensing and sublicensing decisions

3. Editorial and production approval workflow archiving

Data flow: Consonance ? OpenText Extended ECM Platform

When a manuscript, jacket proof, or final page proof is approved in Consonance, the approved version and approval metadata can be archived in OpenText Extended ECM Platform. This ensures that production, compliance, and downstream distribution teams always reference the approved asset set, not earlier drafts.

• Prevents use of outdated files in print, digital, or audio production
• Supports compliance with approval and sign-off requirements
• Provides a permanent record of editorial decisions

4. Metadata synchronization for governed content access

Data flow: Bi-directional

Consonance title metadata such as ISBN, imprint, author, edition, format, and publication date can be synchronized with OpenText Extended ECM Platform to classify and organize related content. In return, OpenText can expose document status, retention category, and access permissions back to Consonance so publishing teams can see whether a title package is complete and compliant.

• Improves search and retrieval across title-related content
• Ensures consistent metadata across publishing and content governance systems
• Helps teams identify missing documents before publication milestones

5. Secure collaboration with external contributors

Data flow: Consonance ? OpenText Extended ECM Platform ? Consonance

Authors, freelancers, translators, and designers often need controlled access to working files. Consonance can initiate the workflow and OpenText Extended ECM Platform can manage secure document sharing, access controls, and external collaboration spaces. Once files are reviewed or updated, the latest versions and status updates can be pushed back into Consonance for project tracking.

• Reduces email-based file exchange and version confusion
• Improves security for sensitive pre-publication materials
• Keeps project managers informed of external review progress

6. Publication package assembly and release management

Data flow: Consonance ? OpenText Extended ECM Platform

As a title moves toward release, Consonance can trigger the creation of a complete publication package in OpenText Extended ECM Platform, including final manuscript, cover files, metadata sheets, legal approvals, and marketing assets. This package can then be governed, retained, and distributed to internal stakeholders or downstream systems with confidence that all required components are present.

• Speeds up release readiness checks
• Creates a standardized title package for print, ebook, and audio workflows
• Supports downstream distribution and compliance review

7. Retention, compliance, and archival of published title records

Data flow: Consonance ? OpenText Extended ECM Platform

After publication, Consonance can send final title records, royalty-related documents, and publication artifacts to OpenText Extended ECM Platform for long-term retention and compliance management. This is especially valuable for publishers that must preserve evidence of publication history, contractual obligations, and rights decisions over many years.

• Supports records management and legal hold requirements
• Reduces risk associated with lost or incomplete title documentation
• Provides a structured archive for audits and disputes

8. Operational reporting across publishing and content governance

Data flow: Bi-directional

Consonance project milestones, title status, and production timelines can be combined with OpenText Extended ECM Platform document activity, approval status, and repository usage to create a more complete operational view. Publishing operations leaders can identify bottlenecks such as delayed approvals, missing legal documents, or stalled asset delivery before they affect launch dates.

• Improves visibility into end-to-end publishing performance
• Helps teams prioritize titles at risk of delay
• Supports better coordination between editorial, legal, production, and IT teams