Consonance - OpenText Content Metadata Service - Dictionary Integration and Automation

Common Integration Use Cases Between Consonance and OpenText Content Metadata Service - Dictionary

1. Standardize publishing metadata across manuscripts, titles, and assets

Consonance can synchronize title, contributor, imprint, format, and rights metadata with OpenText Content Metadata Service - Dictionary so that all publishing teams use the same controlled vocabulary and field definitions. This reduces inconsistent tagging across editorial, production, and rights workflows and improves downstream accuracy for distribution, reporting, and retailer feeds.

• Direction: Consonance to OpenText Content Metadata Service - Dictionary
• Business value: Fewer metadata errors, faster title setup, and better consistency across systems

2. Govern metadata schema changes for new publishing formats and imprints

When Consonance introduces new metadata needs for audio, digital, or special edition workflows, OpenText Content Metadata Service - Dictionary can serve as the master schema governance layer. Metadata administrators define approved fields, data types, and picklists in OpenText, then publish those definitions to Consonance so editorial and production teams capture the right information from the start.

• Direction: OpenText Content Metadata Service - Dictionary to Consonance
• Business value: Faster rollout of new metadata requirements and reduced rework from schema drift

3. Enforce rights and royalty classification consistency

Consonance manages rights and royalty data for authors, territories, and formats, while OpenText Content Metadata Service - Dictionary can enforce standardized rights classifications, royalty types, and territory codes. This helps legal, finance, and rights teams avoid mismatched terminology and ensures that contractual metadata is captured consistently across titles and agreements.

• Direction: Bi-directional
• Business value: Improved rights accuracy, cleaner royalty reporting, and fewer contract interpretation issues

4. Improve metadata quality for digital asset and cover image workflows

Consonance often links cover art, jacket copy, and marketing assets to title records. By integrating with OpenText Content Metadata Service - Dictionary, publishers can apply governed metadata standards to asset classifications such as format, language, edition, market, and usage rights. This ensures that assets attached to a title in Consonance are tagged consistently for reuse across DAM and content repositories.

• Direction: Bi-directional
• Business value: Better asset discoverability, fewer duplicate assets, and stronger rights compliance

5. Support automated validation before title release to distribution channels

Before a title is released from Consonance to distribution systems, metadata can be validated against the controlled dictionary in OpenText Content Metadata Service - Dictionary. Required fields, allowed values, and format rules can be checked automatically to prevent incomplete or noncompliant title records from reaching retailers, wholesalers, or industry databases.

• Direction: OpenText Content Metadata Service - Dictionary to Consonance
• Business value: Fewer rejected feeds, faster publication launches, and reduced manual correction effort

6. Align editorial and production workflows with enterprise metadata governance

Editorial teams in Consonance often create or update metadata early in the publishing lifecycle, while production teams depend on that data later for design, typesetting, and release planning. OpenText Content Metadata Service - Dictionary can provide the authoritative metadata model so both teams work from the same definitions for title status, format, trim size, language, audience, and publication milestones.

• Direction: OpenText Content Metadata Service - Dictionary to Consonance
• Business value: Better workflow coordination, fewer handoff errors, and more reliable production planning

7. Enable enterprise reporting across publishing and content repositories

Consonance tracks publishing pipeline performance, while OpenText Content Metadata Service - Dictionary ensures metadata consistency across content platforms. Together, they enable unified reporting on title status, format mix, rights coverage, and asset readiness across multiple repositories and imprints. This is especially useful for leadership teams that need accurate portfolio views without reconciling inconsistent metadata from different systems.

• Direction: Bi-directional
• Business value: More reliable analytics, improved portfolio visibility, and better decision-making

8. Accelerate onboarding of acquired imprints and legacy catalogs

When a publisher acquires a new imprint or migrates a legacy catalog into Consonance, OpenText Content Metadata Service - Dictionary can provide the standard metadata model used to map and normalize inherited title data. This helps teams convert legacy fields, align controlled values, and load records into Consonance with less manual cleanup and fewer inconsistencies.

• Direction: OpenText Content Metadata Service - Dictionary to Consonance
• Business value: Faster catalog migration, lower data remediation costs, and smoother integration of acquired assets