OpenText Core Content - Metadata - Loci Integration and Automation

Common Integration Use Cases Between OpenText Core Content - Metadata and Loci

1. Metadata-driven content recommendations for internal portals

Flow: OpenText Core Content - Metadata ? Loci

OpenText Core Content - Metadata supplies governed fields such as content type, department, region, product line, and audience segment to Loci. Loci uses this structured metadata alongside user behavior to recommend the most relevant documents, assets, or knowledge articles in employee portals, intranets, and customer-facing content hubs.

Business value: Improves content discoverability, reduces search time, and increases engagement with approved content.

2. Personalized content experiences based on approved taxonomy

Flow: OpenText Core Content - Metadata ? Loci

Controlled vocabularies and validation rules in OpenText ensure that content is consistently tagged before it is exposed to Loci. This allows Loci to build recommendation models around reliable categories such as campaign, lifecycle stage, or compliance status, enabling more accurate personalization across CMS-driven experiences.

Business value: Delivers more precise recommendations and prevents poor-quality tagging from degrading personalization performance.

3. Recommendation feedback to improve metadata governance

Flow: Loci ? OpenText Core Content - Metadata

Loci can return engagement signals such as click-through rates, dwell time, and content affinity by metadata category back to OpenText governance teams. These insights help content owners identify which metadata values are driving discovery and which tags need refinement, consolidation, or retirement.

Business value: Strengthens metadata standards using real usage data and improves content classification decisions.

4. Automated surfacing of high-performing content for editorial teams

Flow: Bi-directional

OpenText provides authoritative metadata for content assets, while Loci identifies which assets are performing best for specific audiences. Editorial and marketing teams can use this combined view to prioritize content updates, promote top-performing assets, and retire underperforming content from recommendation feeds.

Business value: Supports better content lifecycle management and helps teams focus on assets with the highest business impact.

5. Role-based recommendations for employees, partners, or customers

Flow: OpenText Core Content - Metadata ? Loci

OpenText metadata fields such as role, business unit, geography, and access level can be used by Loci to tailor recommendations for different user groups. For example, sales teams can see product battle cards, while compliance teams see policy updates and training materials.

Business value: Increases relevance of content delivery across departments and reduces manual curation effort.

6. Campaign content optimization using metadata and behavior analytics

Flow: Bi-directional

Marketing teams can publish campaign assets in OpenText with standardized metadata such as campaign name, channel, and target persona. Loci then analyzes user interactions and recommends the most effective assets to similar audiences. Performance insights can be fed back to content owners to refine future campaign tagging and asset selection.

Business value: Improves campaign effectiveness, accelerates content reuse, and supports data-driven marketing operations.

7. Compliance-aware recommendations for regulated content environments

Flow: OpenText Core Content - Metadata ? Loci

In regulated industries, OpenText metadata can classify content by approval status, retention category, jurisdiction, or sensitivity level. Loci can use these attributes to ensure only approved and contextually relevant content is recommended to users, reducing the risk of surfacing outdated or non-compliant materials.

Business value: Lowers compliance risk while maintaining a personalized user experience.

8. Content performance reporting for governance and business teams

Flow: Loci ? OpenText Core Content - Metadata

Loci engagement data can be mapped back to OpenText metadata categories and used in reporting dashboards to show which content types, topics, or business units generate the most interaction. Governance, marketing, and knowledge management teams can use this reporting to guide content investment and metadata policy updates.

Business value: Aligns content governance with measurable business outcomes and improves decision-making across teams.