OpenText Content Metadata Service - Dictionary - Kentico Integration and Automation

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

1. Standardized metadata publishing from OpenText to Kentico

Data flow: OpenText Content Metadata Service - Dictionary ? Kentico

Use OpenText Content Metadata Service - Dictionary as the master source for approved metadata fields, data types, and controlled vocabularies, then sync those definitions into Kentico to govern how content is tagged in the digital experience platform. This ensures website editors, marketers, and content teams use consistent categories for pages, assets, campaigns, and product content.

• Improves content consistency across web properties
• Reduces manual tagging errors and duplicate classifications
• Supports more accurate search, filtering, and personalization in Kentico

2. Controlled vocabulary alignment for campaign and landing page tagging

Data flow: OpenText Content Metadata Service - Dictionary ? Kentico

Organizations can push approved taxonomies such as region, product line, audience segment, campaign type, and content lifecycle status from OpenText into Kentico. Marketing teams then apply the same business terms when creating landing pages, campaign assets, and promotional content, which improves reporting and governance.

• Enables consistent campaign reporting across teams
• Supports better audience segmentation and content targeting
• Reduces reliance on ad hoc naming conventions

3. Metadata-driven asset governance for DAM connected to Kentico

Data flow: OpenText Content Metadata Service - Dictionary ? Kentico

When Kentico is connected to a DAM or content repository, OpenText metadata definitions can govern how assets are classified before they are surfaced in Kentico. This is especially useful for images, videos, brochures, and product documents that need reusable metadata for search, rights management, and channel distribution.

• Improves asset discoverability in Kentico content workflows
• Supports reuse of approved assets across web pages and campaigns
• Helps enforce governance for usage rights, expiration, and content status

4. Metadata synchronization for multilingual and regional websites

Data flow: OpenText Content Metadata Service - Dictionary ? Kentico

Global organizations can use OpenText to define standardized metadata for language, market, country, and regulatory region, then apply those definitions in Kentico to manage localized content variants. This helps teams maintain consistent structure across regional websites while allowing local teams to publish content within approved boundaries.

• Supports scalable multi-site and multi-language operations
• Improves governance for regional content ownership
• Reduces inconsistencies in localized publishing processes

5. Content lifecycle status governance for editorial workflows

Data flow: OpenText Content Metadata Service - Dictionary ? Kentico

OpenText can define lifecycle metadata such as draft, approved, expired, archived, or under review, and Kentico can use those values to control editorial workflows and publishing rules. This gives content operations teams a common framework for managing what can be published, reused, or retired.

• Improves control over content approval and expiration
• Reduces risk of publishing outdated or noncompliant content
• Creates clearer handoffs between legal, compliance, and marketing teams

6. Reporting and analytics consistency across content operations

Data flow: OpenText Content Metadata Service - Dictionary ? Kentico

By aligning metadata definitions between OpenText and Kentico, organizations can produce more reliable reports on content performance, asset usage, and campaign effectiveness. Standardized metadata makes it easier to compare results across websites, content repositories, and business units.

• Improves trust in dashboards and operational reports
• Enables cross-team analysis using shared business terms
• Supports better decisions on content investment and optimization

7. Bi-directional governance feedback for metadata refinement

Data flow: Kentico ? OpenText Content Metadata Service - Dictionary

In mature environments, Kentico usage patterns can be reviewed to identify missing, redundant, or underused metadata fields. Governance teams can then update the OpenText dictionary and redistribute the refined schema back to Kentico. This creates a practical feedback loop between content operations and metadata governance.

• Helps keep metadata models aligned with real business usage
• Reduces schema sprawl and unnecessary fields
• Improves adoption by making metadata easier to use in daily workflows