OpenText Core Content - Metadata - Adobe Experience Manager Sites Integration and Automation

Common Integration Use Cases Between OpenText Core Content - Metadata and Adobe Experience Manager Sites

1. Metadata-driven content publishing from OpenText Core Content - Metadata to Adobe Experience Manager Sites

Marketing and content operations teams can manage approved content assets in OpenText Core Content - Metadata with required fields such as campaign, region, product line, audience, and expiry date. Once metadata is validated, the content can be pushed to Adobe Experience Manager Sites for page assembly and publishing.

• Direction: OpenText Core Content - Metadata to Adobe Experience Manager Sites
• Business value: Reduces manual rekeying, improves content quality, and ensures only properly classified content is published
• Typical users: Content operations, web publishing, digital marketing

2. Controlled vocabulary synchronization for consistent site taxonomy

OpenText Core Content - Metadata can act as the system of record for controlled vocabularies such as product categories, regions, brands, and content types. These values can be synchronized with Adobe Experience Manager Sites to standardize page properties, component metadata, and tagging across the website.

• Direction: Bi-directional or OpenText Core Content - Metadata to Adobe Experience Manager Sites
• Business value: Improves searchability, content governance, and reporting consistency across digital channels
• Typical users: Information architects, web administrators, governance teams

3. Metadata validation before content approval and site deployment

Before content is approved for use in Adobe Experience Manager Sites, OpenText Core Content - Metadata can enforce required metadata rules, such as mandatory legal disclaimers, market eligibility, or content owner assignment. Content that fails validation can be routed back for correction before it reaches the website.

• Direction: OpenText Core Content - Metadata to Adobe Experience Manager Sites
• Business value: Reduces compliance risk and prevents incomplete or noncompliant content from going live
• Typical users: Compliance teams, legal reviewers, web content approvers

4. Region-specific content delivery using metadata filters

Adobe Experience Manager Sites can consume metadata from OpenText Core Content - Metadata to determine which assets or page fragments are eligible for specific markets, languages, or business units. This enables localized experiences without duplicating content management effort.

• Direction: OpenText Core Content - Metadata to Adobe Experience Manager Sites
• Business value: Speeds regional publishing and reduces the risk of showing the wrong content to the wrong audience
• Typical users: Global marketing teams, localization teams, regional web managers

5. Content lifecycle management with expiry and review metadata

OpenText Core Content - Metadata can store lifecycle attributes such as publish date, review date, and expiration date. Adobe Experience Manager Sites can use these values to automatically unpublish outdated pages or replace expired content with approved alternatives.

• Direction: OpenText Core Content - Metadata to Adobe Experience Manager Sites
• Business value: Keeps websites current, reduces manual maintenance, and supports regulatory or promotional time limits
• Typical users: Web operations, campaign managers, compliance teams

6. Search and personalization enhancement through enriched metadata

Metadata from OpenText Core Content - Metadata can be passed into Adobe Experience Manager Sites to improve internal search relevance, content recommendations, and audience segmentation. For example, product pages can be tagged with industry, persona, and funnel stage to support more targeted experiences.

• Direction: OpenText Core Content - Metadata to Adobe Experience Manager Sites
• Business value: Improves content discoverability and enables more relevant digital experiences
• Typical users: Digital experience teams, personalization specialists, search administrators

7. Feedback loop for content usage and governance reporting

Adobe Experience Manager Sites can send usage signals such as page association, publish status, and content performance back to OpenText Core Content - Metadata. This allows governance teams to understand which content is actively used, which assets are underperforming, and where metadata quality needs improvement.

• Direction: Adobe Experience Manager Sites to OpenText Core Content - Metadata
• Business value: Supports governance reporting, content rationalization, and better metadata stewardship
• Typical users: Content governance teams, analytics teams, repository administrators

8. Centralized approval workflow for web content reuse

Teams can manage master content records in OpenText Core Content - Metadata and reuse them across multiple Adobe Experience Manager Sites pages. When a master record is updated or reapproved, the change can flow to all dependent site pages, ensuring consistency across campaigns, product launches, and corporate communications.

• Direction: Bi-directional
• Business value: Reduces duplicate content maintenance and improves consistency across channels
• Typical users: Content owners, brand teams, web publishers