OpenText Content Metadata Service - LionBridge Integration and Automation

Common Integration Use Cases Between OpenText Content Metadata Service and Lionbridge

1. Metadata-Driven Translation Job Creation

Flow: OpenText Content Metadata Service ? Lionbridge

When content is tagged with metadata such as language, region, audience, or content type in OpenText Content Metadata Service, those attributes can automatically trigger translation requests in Lionbridge. This ensures only the right assets are sent for localization, with the correct language pairs, priority, and workflow rules applied.

• Reduces manual handoff between content and localization teams
• Improves translation accuracy by using standardized metadata
• Speeds up global publishing for multilingual content

2. Localization Status Updates Back to Metadata Records

Flow: Lionbridge ? OpenText Content Metadata Service

As translation progresses in Lionbridge, status updates such as submitted, in progress, reviewed, and completed can be written back to OpenText Content Metadata Service. This gives content owners and operations teams a single view of localization status alongside the original content metadata.

• Improves visibility into translation pipeline progress
• Supports better release planning for global campaigns
• Reduces status-checking across multiple systems

3. Automated Language Variant Classification

Flow: Bi-directional

OpenText Content Metadata Service can store the master metadata model for language variants, while Lionbridge can return localized asset identifiers, target language codes, and version references. This creates a consistent classification structure for original and translated content across repositories and regions.

• Ensures translated assets inherit the correct metadata structure
• Prevents duplicate or misclassified language versions
• Supports search, retrieval, and governance across global content libraries

4. Region-Specific Content Routing Based on Metadata

Flow: OpenText Content Metadata Service ? Lionbridge

Content tagged for specific markets, business units, or regulatory regions can be routed to Lionbridge only when localization is required. For example, product documentation marked for EMEA or APAC can be automatically sent for translation, while content intended for a single market can bypass the localization workflow.

• Optimizes translation spend by avoiding unnecessary localization
• Enforces market-specific content policies
• Improves operational control over global content distribution

5. Metadata-Enriched Translation Briefs

Flow: OpenText Content Metadata Service ? Lionbridge

OpenText Content Metadata Service can provide Lionbridge with key metadata such as content purpose, product line, legal sensitivity, and target audience. This metadata can be used to generate richer translation briefs, helping linguists apply the correct terminology, tone, and compliance requirements.

• Improves translation quality and consistency
• Reduces rework caused by unclear context
• Supports regulated industries with stricter content controls

6. Reusable Metadata Models for Localization Workflows

Flow: OpenText Content Metadata Service ? Lionbridge

Standardized metadata models from OpenText Content Metadata Service can be reused to define localization workflow rules in Lionbridge. This is especially useful for enterprises managing multiple content repositories, where the same metadata taxonomy can drive consistent translation processes across teams and platforms.

• Creates a common metadata language across systems
• Simplifies governance for enterprise content operations
• Supports scalable rollout across multiple repositories

7. Translation Audit and Compliance Tracking

Flow: Bi-directional

OpenText Content Metadata Service can store compliance-related metadata such as approval status, content owner, and retention class, while Lionbridge can return translation audit details such as translator, review stage, and completion timestamps. Together, they provide a complete audit trail for localized content.

• Supports compliance and governance requirements
• Improves traceability for regulated content
• Makes audit preparation faster and more reliable