Home | Connectors | Consonance | Consonance - OpenText Content Metadata Service Integration and Automation
Consonance and OpenText Content Metadata Service complement each other well in a publishing environment where structured title data, editorial workflows, and reusable metadata standards must stay aligned across systems. Consonance manages the publishing lifecycle, while OpenText Content Metadata Service provides centralized, standardized metadata governance that can be reused across content repositories and applications.
Data flow: OpenText Content Metadata Service to Consonance
Use OpenText Content Metadata Service as the master source for standardized metadata fields such as title, subtitle, author, imprint, BISAC categories, language, format, and rights attributes. Consonance can consume these controlled metadata definitions when new titles are created or updated, ensuring editorial, production, and rights teams work from a consistent schema.
Data flow: Consonance to OpenText Content Metadata Service
When a manuscript or title record is created in Consonance, the platform can send metadata to OpenText Content Metadata Service for validation against approved business rules and required fields. If data is incomplete or inconsistent, the record can be flagged back in Consonance for correction before production begins.
Data flow: Bi-directional
Publishing organizations often manage metadata across editorial systems, digital asset repositories, rights systems, and distribution platforms. OpenText Content Metadata Service can provide a shared metadata model that Consonance uses for title records, while Consonance can publish approved updates back to OpenText so other repositories remain aligned.
Data flow: Bi-directional
Consonance manages rights tracking for titles, territories, formats, and licensing windows. OpenText Content Metadata Service can store standardized rights metadata definitions and classification rules, while Consonance sends rights updates such as territory availability, embargo dates, and license status for reuse in other OpenText-connected repositories.
Data flow: OpenText Content Metadata Service to Consonance
OpenText Content Metadata Service can provide metadata rules that trigger workflow automation in Consonance. For example, when a title is classified as print plus ebook plus audio, Consonance can automatically route tasks to the appropriate production teams, assign format-specific milestones, and enforce required deliverables based on the metadata profile.
Data flow: Consonance to OpenText Content Metadata Service
Once a title is approved in Consonance, final metadata can be pushed to OpenText Content Metadata Service for reuse by connected distribution, search, and content platforms. This helps ensure that the same approved title data is used across retailer feeds, industry databases, and internal content services.
Data flow: Bi-directional
Consonance can provide publishing pipeline and title status data, while OpenText Content Metadata Service supplies standardized classification metadata used to segment reporting by imprint, category, format, language, or market. Together, they enable more reliable analytics on production throughput, catalog performance, and metadata completeness.
Data flow: OpenText Content Metadata Service to Consonance
OpenText Content Metadata Service can define the metadata structure used to classify and link assets such as cover images, author photos, sample chapters, and marketing materials. Consonance can then associate those assets with the correct title records using the shared metadata model, improving discoverability and reducing asset misassignment.
Overall, integrating Consonance with OpenText Content Metadata Service helps publishers enforce metadata consistency, streamline publishing operations, and improve the quality of information flowing from manuscript intake through production, rights management, and distribution.