OpenText Content Metadata Service - Dictionary - Phrase Integration and Automation

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

1. Standardized metadata-driven translation intake

Direction: OpenText Content Metadata Service - Dictionary ? Phrase

When content is sent for localization, OpenText can provide the approved metadata schema for fields such as content type, region, language variant, product line, and legal review status. Phrase uses this metadata to route content into the correct translation workflow, assign the right linguists, and apply the appropriate translation memory or glossary set. This reduces manual setup and ensures every localization job follows the same governance rules.

Business value: Faster project initiation, fewer workflow errors, and more consistent translation handling across teams.

2. Controlled vocabulary synchronization for multilingual content tagging

Direction: OpenText Content Metadata Service - Dictionary ? Phrase

OpenText can act as the system of record for controlled metadata values such as campaign names, product categories, market segments, and content status labels. Phrase can consume these values to ensure translated content is tagged consistently across languages. If new approved terms are added in OpenText, they can be reflected in Phrase so localization teams use the same business terminology in every market.

Business value: Better searchability, cleaner reporting, and reduced risk of inconsistent tagging across localized assets.

3. Localization workflow routing based on content classification

Direction: OpenText Content Metadata Service - Dictionary ? Phrase

Content metadata from OpenText can determine how items are processed in Phrase. For example, marketing copy may go through human translation, while support articles or product descriptions may use machine translation with post-editing. Metadata fields such as content sensitivity, audience type, or publication priority can be used to automatically assign the correct workflow path.

Business value: More efficient localization operations, lower translation costs, and better alignment between content type and translation method.

4. Translation status and language readiness updates back to content governance

Direction: Phrase ? OpenText Content Metadata Service - Dictionary

As translation progresses in Phrase, status updates such as in progress, reviewed, approved, or published can be written back to OpenText metadata fields. This gives content governance, publishing, and compliance teams a single view of which assets are ready for release in each language. It also supports downstream reporting on localization coverage by market or content category.

Business value: Improved visibility, fewer release delays, and stronger governance over multilingual content lifecycles.

5. Metadata-based localization reporting and compliance tracking

Direction: Bi-directional

OpenText provides the authoritative metadata model for reporting dimensions such as business unit, region, content owner, and retention class. Phrase contributes translation metrics such as turnaround time, volume by language, and workflow completion status. Combined, these data sets enable enterprise reporting on localization performance, compliance readiness, and content coverage by market.

Business value: Better operational reporting, stronger auditability, and more informed planning for global content programs.

6. Product content localization with governed metadata for PIM and DAM ecosystems

Direction: OpenText Content Metadata Service - Dictionary ? Phrase

In organizations using OpenText to govern metadata across DAM or ECM repositories, product assets can be tagged with standardized fields such as SKU, product family, launch date, and target market. Phrase can use these fields to localize product descriptions, packaging text, and campaign assets in a structured way. This is especially useful when content must be synchronized across multiple channels and markets.

Business value: Faster product launches, consistent multilingual product information, and reduced rework across content teams.

7. Glossary and terminology governance for regulated or brand-sensitive content

Direction: OpenText Content Metadata Service - Dictionary ? Phrase

OpenText can define approved terminology metadata for regulated terms, brand names, disclaimers, and legal phrases. Phrase can then use these governed terms to support translation consistency and prevent unauthorized wording changes. This is valuable for industries such as healthcare, financial services, and manufacturing where terminology control is critical.

Business value: Lower compliance risk, stronger brand consistency, and fewer terminology-related translation defects.

8. Content lifecycle automation for multilingual publishing

Direction: OpenText Content Metadata Service - Dictionary ? Phrase

OpenText can manage lifecycle metadata such as draft, approved, localized, and archived, while Phrase handles the translation workflow for each language version. Once localization is complete, Phrase can update the content status in OpenText so publishing teams know which assets are ready for release. This creates a closed-loop process for multilingual content operations.

Business value: Less manual coordination, faster publishing cycles, and better end-to-end control of global content delivery.