Home | Connectors | Consonance | Consonance - OpenText Content Metadata Service Integration and Automation

Consonance - OpenText Content Metadata Service Integration and Automation

Integrate Consonance Marketing and OpenText Content Metadata Service Document Management apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

Common Integration Use Cases Between Consonance and OpenText Content Metadata Service

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.

1. Centralized title metadata governance for publishing workflows

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.

  • Reduces duplicate metadata definitions across publishing teams
  • Improves consistency between editorial records and downstream distribution data
  • Supports faster onboarding of new imprints or product lines

2. Automated metadata validation during manuscript and title setup

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.

  • Prevents incomplete title records from moving into production
  • Improves metadata quality before distribution to retailers and industry databases
  • Reduces manual cleanup by editorial operations teams

3. Reusable metadata models across multiple publishing repositories

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.

  • Creates a single metadata structure across the content ecosystem
  • Supports multi-imprint and multi-format publishing operations
  • Reduces integration complexity between systems that rely on the same title data

4. Rights and permissions metadata synchronization

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.

  • Helps legal, rights, and editorial teams work from the same approved rights data
  • Reduces risk of publishing content outside approved territories or formats
  • Improves auditability of rights-related metadata changes

5. Metadata-driven automation for production and publishing milestones

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.

  • Speeds up workflow routing and task assignment
  • Ensures production steps match the intended publishing formats
  • Improves operational control across editorial and production teams

6. Consistent metadata for downstream distribution and retail syndication

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.

  • Improves accuracy of metadata sent to sales channels
  • Reduces discrepancies between internal publishing records and external syndication feeds
  • Supports faster updates when title details change close to publication

7. Metadata standardization for reporting and portfolio analytics

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.

  • Improves executive reporting across publishing portfolios
  • Enables better analysis by title type, market, and format
  • Supports data-driven decisions on scheduling and resource allocation

8. Metadata governance for digital asset and title linkage

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.

  • Strengthens linkage between title records and supporting assets
  • Improves efficiency for marketing, design, and production teams
  • Reduces errors when assets are reused across multiple editions or formats

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.

How to integrate and automate Consonance with OpenText Content Metadata Service using OneTeg?