Consonance - OpenText Core Transformation Publication Service Integration and Automation

Common Integration Use Cases Between Consonance and OpenText Core Transformation Publication Service

1. Automated multi format book output generation

Flow: Consonance to OpenText Core Transformation Publication Service

When a manuscript reaches a production-ready state in Consonance, the title metadata, final content package, and format requirements can be sent to OpenText Core Transformation Publication Service to generate standardized print, PDF, EPUB, and other distribution-ready outputs. This reduces manual file handling between editorial and production teams and ensures each release uses approved source content and consistent formatting rules.

Business value: Faster production cycles, fewer formatting errors, and more reliable delivery of publication assets across channels.

2. Controlled publication of regulated or compliance sensitive titles

Flow: Consonance to OpenText Core Transformation Publication Service

For publishers handling legal, educational, medical, or government related content, Consonance can trigger OpenText Core Transformation Publication Service to produce controlled, standardized outputs from approved content only. Versioned manuscripts, rights cleared assets, and final metadata from Consonance can be published through a governed transformation process that supports auditability and consistent presentation.

Business value: Stronger compliance control, reduced risk of publishing unapproved content, and improved audit readiness.

3. Automated release of title packages to downstream distribution channels

Flow: Consonance to OpenText Core Transformation Publication Service to distribution systems

Consonance can provide the final title record, while OpenText Core Transformation Publication Service generates the standardized output files needed for retailers, wholesalers, libraries, or internal distribution portals. The transformed publication package can then be pushed onward with the correct metadata, format, and version information.

Business value: More efficient title launch operations, fewer rework cycles, and better consistency across sales channels.

4. Re publication of revised editions and corrected content

Flow: Consonance to OpenText Core Transformation Publication Service

When editors update a manuscript, correct an erratum, or release a new edition in Consonance, the updated content can automatically be sent to OpenText Core Transformation Publication Service for regeneration of all required output formats. This supports rapid replacement of outdated files and ensures downstream teams receive the latest approved version without manual intervention.

Business value: Shorter turnaround for corrections, lower risk of stale content being distributed, and improved version control.

5. Standardized production of marketing and review copies

Flow: Consonance to OpenText Core Transformation Publication Service

Marketing, publicity, and sales teams often need review copies, advance reader copies, or catalog proofs in specific formats. Consonance can supply the title metadata and approved content, while OpenText Core Transformation Publication Service creates consistent output files for internal review, sales enablement, and promotional use.

Business value: Faster availability of review materials, reduced dependency on production staff, and more consistent branded outputs.

6. Metadata driven output routing by format, imprint, or market

Flow: Bi directional

Consonance can send title metadata such as imprint, territory, language, and format requirements to OpenText Core Transformation Publication Service so the correct output template is applied. In return, OpenText Core Transformation Publication Service can send back publication status, output identifiers, and file completion details to Consonance for workflow tracking and release governance.

Business value: Better automation across complex publishing portfolios, improved visibility for project managers, and fewer manual routing decisions.

7. Production status feedback for editorial and rights teams

Flow: OpenText Core Transformation Publication Service to Consonance

Once content has been transformed and published, OpenText Core Transformation Publication Service can return completion status, output timestamps, and file references to Consonance. Editorial, production, and rights teams can then see exactly which formats have been generated and released, helping them coordinate approvals, licensing obligations, and launch readiness.

Business value: Better cross team coordination, improved transparency, and faster issue resolution when production delays occur.

8. Centralized archive of final published outputs linked to title records

Flow: OpenText Core Transformation Publication Service to Consonance

After publication, final rendered outputs from OpenText Core Transformation Publication Service can be linked back to the corresponding title record in Consonance as the authoritative published version. This creates a single operational view of the manuscript, final outputs, and publication history, which is useful for audits, reprints, and future edition planning.

Business value: Stronger content traceability, easier retrieval of published files, and improved lifecycle management for backlist and reprint titles.