Consonance - OpenText Core Content - Metadata Integration and Automation

Common Integration Use Cases Between Consonance and OpenText Core Content - Metadata

1. Enforce standardized title metadata across publishing workflows

Data flow: OpenText Core Content - Metadata ? Consonance

Use OpenText Core Content - Metadata as the system of record for controlled metadata fields such as title type, imprint, subject taxonomy, language, rights territory, and content classification. Consonance can consume these governed values when new titles are created or updated, ensuring editorial, production, and rights teams work from approved metadata standards.

Business value: Reduces metadata errors, improves downstream reporting, and ensures consistency across manuscripts, production records, and distribution feeds.

2. Publish approved cover art and marketing assets with validated metadata

Data flow: Bi-directional

When design or marketing teams store cover images, author photos, and promotional files in OpenText Core Content, metadata rules can classify and validate each asset by title, format, campaign, and usage rights. Consonance can then link those approved assets directly to the relevant book record for production and publication workflows.

Business value: Prevents use of unapproved assets, speeds up creative handoffs, and improves traceability between content files and title metadata.

3. Automate metadata-driven workflow routing for editorial and production tasks

Data flow: OpenText Core Content - Metadata ? Consonance

Metadata classifications in OpenText Core Content can trigger workflow rules in Consonance. For example, a manuscript tagged as translated, illustrated, or high priority can automatically route to the correct editorial queue, assign specialized production steps, or require additional approvals before release.

Business value: Shortens cycle times, reduces manual triage, and ensures the right teams handle the right content at the right stage.

4. Improve rights and permissions governance for published content

Data flow: Bi-directional

OpenText Core Content can store governed metadata for rights status, embargo dates, territory restrictions, and license terms. Consonance can use that metadata to control publication schedules and prevent release of content outside approved rights windows. In return, Consonance can update OpenText when rights are renewed, expired, or amended during the publishing lifecycle.

Business value: Reduces compliance risk, avoids accidental publication violations, and gives rights teams better visibility into content status.

5. Strengthen search and discovery for publishing teams

Data flow: Consonance ? OpenText Core Content - Metadata

Consonance can push title and project metadata into OpenText Core Content to improve searchability across editorial assets, contracts, production files, and supporting documents. Structured metadata such as author, series, ISBN, format, and publication status can be used to make content easier to find and filter across repositories.

Business value: Reduces time spent searching for files, improves reuse of content assets, and supports faster decision-making across departments.

6. Support metadata governance for multi-format publishing

Data flow: OpenText Core Content - Metadata ? Consonance

For publishers releasing print, ebook, and audio versions, OpenText Core Content can define mandatory metadata fields and validation rules for each format. Consonance can use those rules to ensure format-specific attributes such as trim size, file type, narrator, audio duration, or accessibility metadata are complete before publication.

Business value: Improves release quality, reduces rework, and helps ensure each format meets channel and retailer requirements.

7. Create a governed archive of final publication packages

Data flow: Consonance ? OpenText Core Content - Metadata

After a title is published, Consonance can send final manuscripts, cover files, production proofs, and release metadata into OpenText Core Content for long-term retention and classification. OpenText can apply retention labels, metadata standards, and access controls to support auditability and future reuse.

Business value: Establishes a reliable archive for compliance, reduces duplication of final assets, and supports future editions or reprints.

8. Enable cross-team reporting on publishing readiness and content status

Data flow: Bi-directional

Consonance provides project and publication milestone data, while OpenText Core Content contributes metadata quality and classification status. Together, they can support dashboards that show which titles are fully metadata-complete, which assets are missing approvals, and which projects are blocked by governance issues.

Business value: Gives editorial, production, and operations leaders a clearer view of publishing readiness, helping them prioritize work and reduce launch delays.