OpenText Core Content - Metadata - Phrase Strings Integration and Automation

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

• Localized content metadata governance for multilingual assets
  Use OpenText Core Content - Metadata to define required fields such as language, region, product line, and content type for assets managed in Phrase Strings. This helps localization teams consistently classify source strings, translated variants, and approved copy across markets. Data flow: OpenText Core Content - Metadata to Phrase Strings.
• Controlled vocabulary synchronization for translation projects
  Maintain approved terminology, campaign names, product labels, and market-specific descriptors in OpenText Core Content - Metadata and push those controlled values into Phrase Strings as reference metadata for translators. This reduces inconsistent translations and supports brand compliance across languages. Data flow: OpenText Core Content - Metadata to Phrase Strings.
• Translation status and workflow reporting across content repositories
  Capture metadata in OpenText Core Content - Metadata for each string set, such as translation status, owner, due date, and target locale, then use it to track progress in Phrase Strings. Business teams can report on localization throughput, overdue assets, and release readiness without manual reconciliation. Data flow: Bi-directional.
• Metadata-driven routing of content to localization teams
  Apply validation rules in OpenText Core Content - Metadata to classify content by business unit, priority, or regulatory sensitivity, then automatically route the corresponding string files in Phrase Strings to the right translation workflow or vendor group. This improves turnaround time and reduces manual assignment errors. Data flow: OpenText Core Content - Metadata to Phrase Strings.
• Audit-ready localization governance for regulated content
  Store compliance-related metadata in OpenText Core Content - Metadata, such as approval status, legal review required, and publication region, and synchronize it with Phrase Strings to ensure only approved content is translated and released. This supports traceability for regulated industries such as healthcare, finance, and manufacturing. Data flow: Bi-directional.
• Search and retrieval of localized assets by metadata
  Use OpenText Core Content - Metadata to enrich Phrase Strings content with structured tags like campaign, product version, and locale. Teams can then quickly find the correct source strings, translation memories, and approved variants for reuse in future releases. Data flow: Phrase Strings to OpenText Core Content - Metadata.
• Release coordination between content governance and localization
  When a content package is marked complete in OpenText Core Content - Metadata, trigger a corresponding localization job in Phrase Strings. Once translations are finalized, update metadata back in OpenText Core Content - Metadata to indicate readiness for publication. This creates a tighter handoff between content operations and product or marketing release cycles. Data flow: Bi-directional.