OpenText Content Metadata Service - Dictionary - LionBridge Integration and Automation

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

1. Metadata-driven translation request creation

Data flow: OpenText Content Metadata Service - Dictionary ? LionBridge

When content is marked with standardized metadata such as language, region, content type, audience, and priority in OpenText Content Metadata Service - Dictionary, those values can automatically trigger translation jobs in Lionbridge. This ensures only the right assets are sent for localization, with the correct target languages and service levels.

• Reduces manual handoff between content and localization teams
• Improves translation accuracy by passing consistent metadata
• Supports faster launch of multilingual campaigns and product content

2. Controlled vocabulary alignment for localization workflows

Data flow: Bi-directional

OpenText Content Metadata Service - Dictionary can provide governed terms for content classification, while Lionbridge can return localization status or language-specific metadata using the same controlled vocabulary. This keeps terminology consistent across source and translated assets, especially for regulated or brand-sensitive content.

• Ensures consistent tagging across languages and repositories
• Improves reporting on translation status and content readiness
• Reduces errors caused by inconsistent labels or free-text values

3. Automated routing of content by locale and market

Data flow: OpenText Content Metadata Service - Dictionary ? Lionbridge

Metadata fields such as market, country, product line, and content owner can be used to route content to the correct localization workflow in Lionbridge. For example, a product sheet tagged for France and Canada French can be automatically sent to the appropriate translation queue with the right locale rules.

• Speeds up localization intake and assignment
• Reduces misrouting of content to the wrong language team
• Supports market-specific publishing requirements

4. Translation status synchronization back to content governance

Data flow: Lionbridge ? OpenText Content Metadata Service - Dictionary

As translation progresses in Lionbridge, status updates such as submitted, in progress, reviewed, approved, or rejected can be written back to OpenText Content Metadata Service - Dictionary as governed metadata values. This gives content managers and governance teams a single view of localization progress across repositories.

• Improves visibility into multilingual content readiness
• Supports better release planning and dependency management
• Enables reporting on bottlenecks and turnaround times

5. Metadata-enriched translation package preparation

Data flow: OpenText Content Metadata Service - Dictionary ? Lionbridge

Before content is sent for translation, OpenText Content Metadata Service - Dictionary can supply structured metadata such as subject area, product family, legal sensitivity, and reuse eligibility. Lionbridge can use this context to apply the correct translation workflow, reviewer assignment, and quality checks.

• Improves translation quality through better context
• Helps prioritize high-value or time-sensitive content
• Reduces rework caused by missing source context

6. Multilingual asset governance for DAM and ECM environments

Data flow: Bi-directional

In organizations using OpenText for content governance and Lionbridge for localization, metadata can be used to track original and translated asset relationships across systems. Source assets, translated versions, and approved variants can all share common identifiers and classification values, making it easier to manage version control and reuse.

• Supports traceability between source and localized assets
• Improves governance over approved language variants
• Reduces duplication and orphaned translated files

7. Compliance and regulated-content localization tracking

Data flow: Bi-directional

For regulated industries such as healthcare, financial services, or manufacturing, OpenText Content Metadata Service - Dictionary can define compliance-related metadata such as jurisdiction, approval status, and retention class. Lionbridge can use these values to apply the correct translation process and return completion data for audit and compliance reporting.

• Supports controlled handling of sensitive content
• Improves auditability of multilingual compliance workflows
• Helps ensure only approved content is localized and published

8. Localization analytics and reporting standardization

Data flow: Lionbridge ? OpenText Content Metadata Service - Dictionary

Translation metrics from Lionbridge, such as turnaround time, language pair, content volume, and workflow outcome, can be mapped back into OpenText Content Metadata Service - Dictionary using standardized metadata fields. This allows enterprise reporting teams to analyze localization performance alongside broader content operations data.

• Creates consistent reporting across content and translation operations
• Helps identify high-cost languages or slow approval steps
• Supports continuous improvement in global content delivery