Home | Connectors | OpenText Content Metadata Service | OpenText Content Metadata Service - OpenText Core Experience Insights Integration and Automation
OpenText Content Metadata Service centralizes and standardizes metadata across content repositories, while OpenText Core Experience Insights measures how users interact with content and applications. Together, they can connect content governance with usage analytics to improve discoverability, adoption, and operational decision-making.
Data flow: OpenText Content Metadata Service to OpenText Core Experience Insights
Push standardized metadata such as content type, department, region, retention class, and business process tags into Core Experience Insights so analytics can segment engagement by content category. This helps teams identify which document classes are most viewed, which metadata structures drive better search performance, and where users abandon content journeys.
Data flow: OpenText Core Experience Insights to OpenText Content Metadata Service
Use interaction data such as failed searches, low-click search results, and frequent refinements to identify gaps in metadata quality. Feed these findings back into the metadata service to refine controlled vocabularies, add missing attributes, or adjust classification rules. This improves findability and reduces time spent searching for content.
Data flow: Bi-directional
When a new metadata model is introduced, Content Metadata Service provides the approved schema and field definitions, while Core Experience Insights tracks whether users are completing required fields, how often they use the new model, and where they struggle. Business and governance teams can use this to measure rollout success and target training or form redesign efforts.
Data flow: Bi-directional
Combine metadata governance data with usage analytics to show whether governed content is actually being used. For example, compare content tagged as policy, procedure, or approved reference material against access frequency, repeat visits, and user engagement. This supports records management, compliance, and content rationalization decisions.
Data flow: OpenText Core Experience Insights to OpenText Content Metadata Service
Analyze how different user groups interact with content by role, business unit, or geography, then use the results to adjust metadata requirements and default classifications. For example, if sales teams consistently access product collateral by region, the metadata model can be updated to prioritize regional attributes and improve content filtering.
Data flow: Bi-directional
Use metadata such as retention status, content owner, and review date from the metadata service alongside engagement metrics from Core Experience Insights to identify stale but heavily used content, or newly published content that is not being adopted. This enables content owners to prioritize updates, retire obsolete assets, and focus governance efforts where business impact is highest.
Data flow: OpenText Content Metadata Service to OpenText Core Experience Insights
Standard metadata definitions can be used to benchmark experience across repositories, teams, or business units. Core Experience Insights can then compare engagement patterns for similar content types across different environments, helping enterprise teams identify where metadata consistency supports better adoption and where local variations are causing friction.
Data flow: OpenText Core Experience Insights to OpenText Content Metadata Service
Correlate user behavior signals such as repeated searches, short session duration, and low content interaction with metadata completeness and consistency. The resulting analysis can highlight which metadata fields are most valuable to users and which ones add administrative burden without improving experience, enabling more practical metadata governance.
These integrations help organizations connect content structure with real usage data, improving governance, search relevance, user adoption, and continuous optimization across the content ecosystem.