OpenText Core Content - Metadata - Phrase Integration and Automation

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

OpenText Core Content - Metadata and Phrase complement each other well in enterprises that manage large volumes of governed content and need that content localized for global audiences. OpenText Core Content - Metadata provides structured metadata control, validation, and classification, while Phrase manages translation workflows, linguistic consistency, and multilingual delivery. Together, they help teams localize content faster while preserving governance, searchability, and compliance.

1. Metadata-driven translation routing for content localization

When content is created or updated in OpenText Core Content - Metadata, key metadata fields such as content type, region, language, product line, and priority can be sent to Phrase to determine the correct translation workflow. This ensures that only eligible content is routed for localization and that the right linguists or machine translation engines are assigned based on content category and market.

• Direction: OpenText Core Content - Metadata to Phrase
• Business value: Reduces manual triage, speeds up localization intake, and improves translation accuracy through metadata-based workflow rules.

2. Return translated content with governed metadata for publishing

After translation is completed in Phrase, the translated assets or text can be sent back to OpenText Core Content - Metadata with the appropriate language, locale, version, and approval metadata applied. This allows content teams to maintain a single governed repository while publishing localized versions with consistent classification and traceability.

• Direction: Phrase to OpenText Core Content - Metadata
• Business value: Improves content control, supports auditability, and ensures translated assets are stored with the same governance standards as source content.

3. Controlled vocabulary enforcement for multilingual terminology consistency

OpenText Core Content - Metadata can maintain approved terminology, product names, and category values that must be used across content. These controlled vocabularies can be shared with Phrase to support translation memory, glossary management, and terminology validation, helping translators use approved terms consistently across languages and channels.

• Direction: Bi-directional
• Business value: Reduces terminology drift, strengthens brand consistency, and lowers rework caused by inconsistent translations.

4. Automated localization of DAM assets and associated metadata

For organizations managing digital assets in OpenText Core Content - Metadata, asset metadata such as campaign name, usage rights, audience segment, and region can trigger translation of captions, descriptions, alt text, and supporting copy in Phrase. This is especially useful for global marketing teams that need localized assets ready for regional campaigns.

• Direction: OpenText Core Content - Metadata to Phrase, then Phrase to OpenText Core Content - Metadata
• Business value: Accelerates campaign readiness, improves asset reuse across markets, and ensures localized metadata is available alongside the asset.

5. Localization workflow based on content status and approval metadata

OpenText Core Content - Metadata can use status fields such as draft, approved, legal review, or ready for translation to control when content is sent to Phrase. This prevents premature translation of content that is still changing and ensures only approved source content enters the localization process.

• Direction: OpenText Core Content - Metadata to Phrase
• Business value: Avoids wasted translation effort, reduces version conflicts, and improves coordination between content owners, legal, and localization teams.

6. Multilingual content synchronization for regulated documentation

In regulated industries, source documents stored in OpenText Core Content - Metadata can be translated in Phrase and then synchronized back with language-specific metadata such as jurisdiction, document type, effective date, and compliance status. This creates a controlled process for maintaining localized policies, manuals, and product documentation.

• Direction: Bi-directional
• Business value: Supports compliance, simplifies document governance, and provides a clear record of localized document versions.

7. Translation request prioritization using metadata-based business rules

OpenText Core Content - Metadata can classify content by business impact, market launch date, or customer-facing priority. That metadata can be used to prioritize translation jobs in Phrase so high-value content is localized first, while lower-priority content follows standard processing. This is useful for product launches, seasonal campaigns, and urgent regulatory updates.

• Direction: OpenText Core Content - Metadata to Phrase
• Business value: Aligns localization capacity with business priorities and improves time to market for critical content.

8. Localization reporting and content governance visibility

Status and metadata from both platforms can be combined to provide reporting on translation volume, turnaround time, content readiness, and language coverage. OpenText Core Content - Metadata supplies structured content attributes, while Phrase provides workflow and translation progress data. Together, they give operations and leadership teams a clearer view of localization performance and content governance.

• Direction: Bi-directional
• Business value: Improves operational visibility, supports SLA tracking, and helps teams identify bottlenecks in content and translation workflows.