OpenText Core Content - Metadata - Bluestone PIM Integration and Automation

Common Integration Use Cases Between OpenText Core Content - Metadata and Bluestone PIM

• 1. Centralized product metadata governance for catalog consistency

  Direction: Bluestone PIM ? OpenText Core Content - Metadata

  Product teams can publish approved product attributes, naming conventions, and classification rules from Bluestone PIM into OpenText Core Content - Metadata to standardize how supporting content is tagged and governed. This ensures that product manuals, spec sheets, compliance documents, and marketing assets use the same controlled vocabulary as the product catalog.

  Business value: Improves search accuracy, reduces duplicate or inconsistent metadata, and gives merchandising, content, and compliance teams a single governance model.

• 2. Automated tagging of product-related documents and assets

  Direction: Bluestone PIM ? OpenText Core Content - Metadata

  When new products or product updates are created in Bluestone PIM, key identifiers such as SKU, product family, brand, category, and market can be pushed to OpenText Core Content - Metadata to auto-tag related documents stored in OpenText. This is especially useful for product data sheets, installation guides, and regulatory files that need to be linked to the correct product record.

  Business value: Reduces manual indexing effort, speeds up content publishing, and improves retrieval of product documentation across teams and channels.

• 3. Controlled vocabulary synchronization for product and content classification

  Direction: Bi-directional

  Bluestone PIM can share product taxonomy values such as category, subcategory, brand hierarchy, and market segment with OpenText Core Content - Metadata, while OpenText can return approved metadata terms used for document classification and governance. This keeps product data and content metadata aligned across systems and prevents mismatched labels between commerce and content repositories.

  Business value: Supports consistent classification across eCommerce, DAM, and ECM processes, reducing rework and improving governance for global product portfolios.

• 4. Compliance document linkage to regulated products

  Direction: Bluestone PIM ? OpenText Core Content - Metadata

  For regulated industries such as manufacturing, healthcare, or chemicals, Bluestone PIM can send product attributes like regulatory class, region, and hazard category to OpenText Core Content - Metadata. OpenText then applies validation rules and metadata requirements to ensure the correct compliance documents are associated with each product record.

  Business value: Helps teams prove compliance faster, lowers the risk of publishing incomplete product information, and supports audit readiness.

• 5. Product launch content readiness workflow

  Direction: Bi-directional

  As a new product moves through launch stages in Bluestone PIM, OpenText Core Content - Metadata can receive launch status, market, and channel metadata to organize supporting assets and documentation. In return, OpenText can provide content readiness status back to Bluestone PIM so product managers know whether required assets, manuals, and localized documents are complete before launch.

  Business value: Improves cross-functional launch coordination between product, marketing, legal, and content teams and reduces launch delays caused by missing assets.

• 6. Enriched search and discovery for product support content

  Direction: Bluestone PIM ? OpenText Core Content - Metadata

  Product identifiers and hierarchy data from Bluestone PIM can be used to enrich metadata in OpenText Core Content - Metadata, making it easier for internal teams and customer support to find the right product documentation. For example, a support agent searching by SKU or product line can quickly retrieve the correct installation guide, warranty document, or troubleshooting file.

  Business value: Reduces time spent searching for content, improves customer service response times, and increases the accuracy of self-service documentation.

• 7. Regional and channel-specific content governance

  Direction: Bluestone PIM ? OpenText Core Content - Metadata

  Bluestone PIM can provide channel, country, language, and market-specific product data to OpenText Core Content - Metadata so that content repositories can enforce region-specific metadata rules. This is useful when different product claims, labels, or documentation versions must be controlled by geography or sales channel.

  Business value: Supports localized commerce operations, reduces publishing errors across regions, and ensures the right content is used in the right market.