Consonance - OpenText Documentum Integration and Automation

Common Integration Use Cases Between Consonance and OpenText Documentum

Consonance and OpenText Documentum complement each other well in publishing environments that require both rich publishing workflow management and enterprise-grade content governance. Consonance manages the editorial, production, rights, and metadata lifecycle for books, while Documentum provides controlled document storage, records management, compliance, and auditability. Together, they can support secure, traceable, and efficient publishing operations across editorial, legal, production, and compliance teams.

1. Controlled manuscript and contract repository for editorial and legal teams

Data flow: Consonance to OpenText Documentum

When a manuscript, author agreement, or rights contract is approved in Consonance, the final version can be automatically archived in Documentum as a controlled record. Consonance retains the workflow context for editorial and production teams, while Documentum becomes the system of record for the signed document, version history, retention policy, and audit trail.

• Reduces risk of using outdated manuscript or contract versions
• Supports legal hold, retention, and compliance requirements
• Gives editorial teams fast access to the latest approved files without losing governance controls

2. Rights and permissions documentation management

Data flow: Bi-directional

Consonance can send rights metadata, territory details, and publication permissions to Documentum, while Documentum stores supporting evidence such as signed licenses, permissions letters, and third-party agreements. This creates a complete rights management record that links structured rights data with the underlying legal documents.

• Improves visibility into what rights are owned, licensed, or restricted
• Helps rights teams respond faster to reuse, translation, and reprint requests
• Provides a defensible audit trail for rights disputes and compliance reviews

3. Approval and sign-off workflow for sensitive publishing assets

Data flow: Consonance to OpenText Documentum

For regulated or high-risk content such as medical, educational, or government-related titles, Consonance can route final manuscripts, cover copy, and production proofs to Documentum for formal review and approval. Documentum can enforce controlled workflows, reviewer assignments, and approval records before Consonance advances the title to publication.

• Ensures mandatory reviews are completed before release
• Supports compliance-heavy publishing programs
• Creates a clear approval record for internal and external audits

4. Centralized storage of production deliverables and source files

Data flow: Consonance to OpenText Documentum

As production teams finalize files such as print-ready PDFs, EPUB packages, cover artwork, and audio scripts in Consonance, those deliverables can be transferred to Documentum for long-term controlled storage. Consonance keeps the operational workflow and publication schedule, while Documentum preserves the authoritative production assets with version control and retention rules.

• Reduces file sprawl across shared drives and email attachments
• Improves retrieval of final assets for reprints, revisions, and audits
• Supports standardized retention of master publishing files

5. Compliance archive for publication history and audit evidence

Data flow: Consonance to OpenText Documentum

Consonance can pass key publication milestones, title metadata snapshots, approval records, and release dates into Documentum to create a compliance archive. This is especially useful for publishers operating in regulated markets or managing government, academic, or professional content where proof of process matters.

• Captures who approved what and when
• Preserves evidence of publication decisions and workflow completion
• Supports internal audits, regulatory reviews, and dispute resolution

6. Secure access to editorial and production documents for distributed teams

Data flow: Bi-directional

Consonance can surface links or embedded references to controlled documents stored in Documentum, allowing editors, designers, and production managers to access the right version without duplicating files. In return, Documentum can receive metadata from Consonance such as title, imprint, project stage, and document type to improve search and classification.

• Improves document findability across departments
• Reduces duplicate storage and version confusion
• Helps remote teams work from a single trusted content source

7. Retention and disposition of obsolete publishing materials

Data flow: Consonance to OpenText Documentum

When a title is superseded, out of print, or moved to archive status in Consonance, the related manuscripts, proofs, and production documents can be transferred to Documentum for records retention and disposition management. Documentum can then apply retention schedules based on legal, contractual, or corporate policy.

• Ensures obsolete content is handled consistently
• Reduces storage and governance burden in Consonance
• Supports defensible records management for legacy titles

8. Cross-system metadata synchronization for discoverability and governance

Data flow: Bi-directional

Consonance can provide title metadata such as ISBN, author, imprint, format, publication status, and rights details to Documentum so documents are indexed in business context. Documentum can return document identifiers, version status, and compliance flags to Consonance to help publishing teams understand whether a file is approved, restricted, or archived.

• Improves search accuracy and document classification
• Aligns publishing workflow data with enterprise content governance
• Reduces manual metadata entry and associated errors

Together, Consonance and OpenText Documentum create a strong operating model for publishers that need both agile publishing execution and rigorous content control. The integration is most valuable where editorial speed must be balanced with legal, compliance, and records management requirements.