Consonance - OpenText Developer Admin - IM Developer Administration Integration and Automation

Common Integration Use Cases Between Consonance and OpenText Developer Admin - IM Developer Administration

1. Publish-ready metadata and asset integration setup for new titles

Data flow: Consonance ? OpenText Developer Admin - IM Developer Administration

When a new book title moves from acquisition into production in Consonance, the title metadata, format requirements, and related workflow identifiers can be passed to OpenText Developer Admin to configure the required integration artifacts, API connections, and messaging routes. This helps integration teams prepare downstream interfaces for cover art, jacket copy, ONIX feeds, or distribution updates before the title reaches publication.

• Reduces manual setup for each new title or imprint
• Ensures integration endpoints are aligned with the title lifecycle
• Supports faster onboarding of new publishing projects

2. Automated environment provisioning for publishing workflow integrations

Data flow: Consonance ? OpenText Developer Admin - IM Developer Administration

Consonance can trigger integration configuration requests when a publisher launches a new workflow, imprint, or product line. OpenText Developer Admin can be used to manage development and test environment credentials, API keys, and messaging configurations needed to validate publishing integrations before release to production. This is especially useful when publishers need separate environments for editorial, production, and distribution testing.

• Improves separation between test and live publishing operations
• Supports controlled rollout of new integrations
• Reduces risk of production data errors during implementation

3. Rights and royalty data exchange with downstream integration services

Data flow: Consonance ? OpenText Developer Admin - IM Developer Administration

Consonance manages rights and royalty information across titles, authors, and territories. OpenText Developer Admin can support the integration services that move this data to finance, royalty accounting, or partner systems by managing the APIs, credentials, and message definitions used in those exchanges. Updates from external systems, such as royalty statements or rights status changes, can be routed back into Consonance through the same controlled integration layer.

• Improves accuracy of royalty and rights records
• Enables controlled exchange with finance and partner platforms
• Supports auditability of sensitive publishing data

4. Distribution feed orchestration for retailers and industry databases

Data flow: Consonance ? OpenText Developer Admin - IM Developer Administration

Consonance holds the authoritative title metadata needed for distribution, including ISBNs, pricing, format details, and publication dates. OpenText Developer Admin can manage the integration components that transform and route this data into retailer feeds, wholesaler systems, and industry databases. This allows integration teams to maintain and update distribution interfaces without changing the publishing workflow application itself.

• Speeds delivery of accurate metadata to sales channels
• Reduces manual feed maintenance across multiple partners
• Supports consistent release of print, digital, and audio metadata

5. Digital asset linkage and validation workflow

Data flow: Consonance ? OpenText Developer Admin - IM Developer Administration

Consonance can send title and asset reference data to integration services managed through OpenText Developer Admin so that cover images, marketing materials, and production files are linked to the correct title records. Validation responses, such as missing files, incorrect formats, or failed transfers, can be sent back to Consonance to alert editorial or production teams before publication.

• Prevents missing or mismatched assets at release time
• Improves coordination between production and integration teams
• Creates a controlled process for asset validation and exception handling

6. Workflow event monitoring and integration exception management

Data flow: Consonance ? OpenText Developer Admin - IM Developer Administration

As manuscripts and titles move through editorial, design, and production stages in Consonance, workflow events can be forwarded to integration services configured in OpenText Developer Admin. These services can monitor event delivery, manage retries, and handle exceptions when downstream systems fail, such as a distribution feed rejection or a missing credential. This gives operations teams a central place to manage integration reliability.

• Improves visibility into publishing workflow dependencies
• Reduces delays caused by failed downstream transactions
• Supports operational support teams with clearer error handling

7. Controlled promotion of integration changes from development to production

Data flow: OpenText Developer Admin - IM Developer Administration ? Consonance

Integration teams can use OpenText Developer Admin to manage versioned APIs, credentials, and messaging artifacts for Consonance-related interfaces, then promote approved changes into production once publishing stakeholders validate them. This is useful when metadata schemas, distribution requirements, or royalty interfaces change and need coordinated deployment across publishing operations.

• Supports change control for business-critical publishing integrations
• Reduces downtime during interface updates
• Helps align IT release cycles with publishing schedules

8. Cross-team governance for publishing and integration operations

Data flow: Bi-directional

Consonance provides the business context for title status, publication milestones, and rights data, while OpenText Developer Admin provides the technical governance for integration artifacts, credentials, and environment separation. Together, they support a governed operating model where editorial, production, distribution, and integration teams can coordinate changes without losing control over data movement or system access.

• Improves collaboration between publishing and integration teams
• Strengthens governance over sensitive title and rights data
• Creates a scalable model for multi-imprint publishing operations