Consonance - OpenText Core Case Integration and Automation

Common Integration Use Cases Between Consonance and OpenText Core Case

Consonance and OpenText Core Case complement each other well when publishers need structured case management around exceptions, disputes, approvals, and issue resolution tied to books, rights, metadata, and production workflows. Consonance manages the publishing lifecycle, while OpenText Core Case adds a unified case view for investigation, review, and resolution.

1. Rights and permissions dispute case management

When a rights conflict, license question, or permissions issue is identified in Consonance, a case can be created in OpenText Core Case with the relevant title metadata, contract references, author details, and supporting documents. Legal, editorial, and rights teams can collaborate in the case workspace to review evidence, track decisions, and record the resolution.

• Data flow: Consonance to OpenText Core Case
• Business value: Faster resolution of rights issues, reduced legal risk, and better auditability

2. Manuscript or title exception handling

If a manuscript misses a milestone, contains missing deliverables, or requires escalation due to editorial or production blockers, Consonance can trigger a case in OpenText Core Case. The case can capture the issue type, impacted title, responsible team, due dates, and related files, enabling structured investigation and accountability across editorial, design, and production teams.

• Data flow: Consonance to OpenText Core Case
• Business value: Improved visibility into bottlenecks and more consistent escalation handling

3. Metadata correction and publication quality review

When metadata validation fails for a title, such as missing ISBN data, incorrect contributor names, or inconsistent format information, Consonance can open a review case in OpenText Core Case. Metadata specialists can assess the issue, attach supporting records, approve corrections, and close the case once the title data is ready for downstream distribution.

• Data flow: Consonance to OpenText Core Case
• Business value: Higher metadata accuracy, fewer downstream retailer errors, and better catalog quality

4. Royalty dispute and payment investigation workflow

Royalty anomalies detected in Consonance, such as disputed statements, unusual deductions, or missing sales feeds, can be routed into OpenText Core Case for investigation. Finance, rights, and sales operations teams can work from a single case record that includes royalty reports, contract terms, sales history, and correspondence with authors or agents.

• Data flow: Consonance to OpenText Core Case, with resolution updates back to Consonance
• Business value: Better control over author disputes, faster investigations, and improved trust in royalty processing

5. Production issue escalation and resolution tracking

If a title encounters a production issue such as a missing cover file, failed proof approval, or delayed vendor delivery, Consonance can create a case in OpenText Core Case. The case can coordinate tasks across production, design, and external vendors, while maintaining a complete record of actions, approvals, and final resolution.

• Data flow: Consonance to OpenText Core Case
• Business value: Reduced delays in publication schedules and stronger cross-team accountability

6. Contract and document review for publishing approvals

OpenText Core Case can manage review cases for publishing approvals that require legal or compliance oversight, such as sensitive content, third-party content usage, or special contractual terms. Consonance can provide the title context, manuscript version, contributor details, and linked assets, while OpenText Core Case manages the review steps and approval evidence.

• Data flow: Bi-directional
• Business value: More controlled approval workflows and better compliance documentation

7. Customer or author complaint resolution tied to a title

When an author, agent, or external stakeholder raises a complaint about a title, schedule, rights usage, or publication quality, OpenText Core Case can manage the complaint as a formal case and link it back to the relevant record in Consonance. Publishing teams can then update title status, add notes, or trigger corrective actions directly from the case outcome.

• Data flow: OpenText Core Case to Consonance, with status updates returned
• Business value: Better stakeholder service, clearer ownership, and faster corrective action

8. Audit trail for publishing exceptions and compliance reviews

For publishers that need a defensible record of decisions, OpenText Core Case can serve as the system of record for exception handling across editorial, rights, and production. Consonance supplies the operational context, while OpenText Core Case stores the case history, attachments, approvals, and final disposition for audit and compliance reporting.

• Data flow: Bi-directional
• Business value: Stronger governance, improved traceability, and easier audit preparation