Home | Connectors | OpenText Content Metadata Service - Dictionary | OpenText Content Metadata Service - Dictionary - Phrase Strings Integration and Automation
Use OpenText Content Metadata Service - Dictionary to define the approved metadata fields for content items, such as language, region, product line, audience, and content type. Sync those controlled values into Phrase Strings so localization teams can tag translation jobs consistently and route content by market. This reduces manual setup errors and ensures translated content is organized using the same enterprise taxonomy across teams.
When content is classified in OpenText using governed metadata, that classification can trigger the correct localization workflow in Phrase Strings. For example, a document tagged as legal, marketing, or technical can automatically be sent to the appropriate translation project template, reviewer group, or approval path. This improves turnaround time and ensures the right stakeholders are involved based on content sensitivity and business purpose.
OpenText can act as the system of record for metadata definitions, while Phrase Strings consumes those definitions to maintain consistent labels and attributes across translated content. This is especially useful for enterprises managing multilingual knowledge bases, product documentation, or policy content. The result is better governance, easier auditability, and more reliable reporting across languages and repositories.
Controlled vocabularies defined in OpenText can be shared with Phrase Strings to standardize product names, department terms, regulatory phrases, and other approved language. This helps translation teams maintain consistency in terminology across all markets and reduces rework caused by conflicting terms. It also supports better translation memory reuse and higher quality localized content.
Metadata in OpenText can identify the target market, country, or business unit for each content item. That information can be passed to Phrase Strings to route content to the correct language combinations, in-country reviewers, or regional translation vendors. This is valuable for global organizations that need different approval chains or content variants for each market.
By aligning metadata definitions between OpenText and Phrase Strings, organizations can report on content status, translation progress, and publication readiness using the same business terms. For example, teams can track how many assets are in draft, in translation, approved, or published by region or content category. This improves operational visibility for content operations, localization managers, and compliance teams.
OpenText metadata can be used to determine when content should move into localization in Phrase Strings, such as when a document reaches approved status or a product release date is approaching. After translation is complete, Phrase Strings can return status updates that OpenText uses to advance the content lifecycle, notify owners, or release assets for publication. This creates a more efficient end to end workflow with fewer manual handoffs.
For regulated industries, OpenText can classify content by risk level, retention policy, or compliance category using governed metadata. That classification can be shared with Phrase Strings to enforce stricter translation workflows, reviewer assignments, and approval checkpoints for sensitive content. This helps ensure that legal, medical, financial, or policy content is translated and reviewed according to enterprise governance standards.