OpenText Content Metadata Service - TransPerfect Integration and Automation

Common Integration Use Cases Between OpenText Content Metadata Service and TransPerfect

• Metadata-driven translation job creation
  When new content is added to OpenText Content Metadata Service with fields such as language, region, content type, and priority, the integration can automatically send the item to TransPerfect for translation or localization. This reduces manual handoffs, ensures the right content is routed to the correct language workflow, and speeds up global publishing.
• Localized content status updates back to the metadata repository
  As TransPerfect completes translation, review, and linguistic QA steps, status updates can be written back to OpenText Content Metadata Service. Teams gain a single view of content readiness by language and market, improving release coordination across marketing, legal, and regional teams.
• Standardized metadata mapping for multilingual content governance
  OpenText Content Metadata Service can act as the system of record for controlled metadata values such as locale, market, product line, and content owner. These values can be passed to TransPerfect to ensure consistent translation instructions, terminology usage, and market-specific handling across all content requests.
• Automated localization of regulated or high-risk content
  For content tagged in OpenText Content Metadata Service as regulated, customer-facing, or legally sensitive, the integration can trigger a specialized TransPerfect workflow that includes translation memory, terminology checks, and human review. This helps reduce compliance risk and ensures approved language is used consistently across regions.
• Reuse of translated assets across repositories
  OpenText Content Metadata Service can store metadata that identifies previously translated content, source language, target language, version, and reuse eligibility. TransPerfect can use this information to avoid duplicate translation work and support translation memory reuse, lowering localization costs and improving turnaround times.
• Regional content publishing orchestration
  When a source asset in OpenText Content Metadata Service is approved for a specific market, the integration can send it to TransPerfect for localization and then return the completed language variants with the correct metadata tags. This supports coordinated publishing across CMS, DAM, and portal environments without manual rekeying of content attributes.
• Multilingual search and discovery enablement
  Translated content returned from TransPerfect can be enriched with standardized metadata from OpenText Content Metadata Service, including language, subject, audience, and geography. This improves search accuracy and content discovery for internal users, regional teams, and external customers working in multiple languages.
• Bi-directional workflow for content updates and retranslation
  If source content changes in OpenText Content Metadata Service, the updated metadata can trigger TransPerfect to identify impacted language versions and initiate retranslation only where needed. This bi-directional approach helps maintain consistency across markets while minimizing unnecessary translation effort.