Home | Connectors | OpenText Content Metadata Service | OpenText Content Metadata Service - Storyteq Integration and Automation
Data flow: Storyteq ? OpenText Content Metadata Service
When creative teams upload campaign assets, Storyteq can send key asset attributes such as campaign name, product line, region, channel, language, and approval status to OpenText Content Metadata Service. OpenText then applies standardized metadata models so assets are consistently classified across repositories and downstream systems.
Data flow: OpenText Content Metadata Service ? Storyteq
Business users can create or update standardized metadata in OpenText, such as brand, market, audience segment, and campaign objective. Storyteq can consume this metadata to auto-populate creative briefs, route requests to the correct design workflow, and ensure the right templates are used for each market or channel.
Data flow: Bi-directional
Once an asset is approved in Storyteq, its final metadata can be synchronized to OpenText Content Metadata Service for enterprise storage, compliance, and reuse. If metadata is updated in OpenText, such as retention class or legal region, those changes can be pushed back to Storyteq to keep creative teams aligned with governance requirements.
Data flow: OpenText Content Metadata Service ? Storyteq
OpenText can provide standardized metadata for country, language, legal entity, and market-specific restrictions. Storyteq can use this information to generate localized creative variants, apply the correct templates, and route assets to the appropriate regional review teams.
Data flow: Storyteq ? OpenText Content Metadata Service
Storyteq can publish completed campaign assets and their metadata to OpenText so marketing operations and brand teams can search by product, audience, format, season, or performance category. This makes it easier to find reusable creative for future campaigns and avoid recreating assets that already exist.
Data flow: OpenText Content Metadata Service ? Storyteq
OpenText can act as the master metadata service defining controlled vocabularies, taxonomy values, and required fields. Storyteq can consume these standards to validate user input during creative production, ensuring that all assets follow the same enterprise metadata rules before publication.
Data flow: Bi-directional
Storyteq workflow states such as draft, in review, approved, and published can be synchronized with OpenText metadata records. This gives marketing, legal, compliance, and content operations teams a shared view of asset status without needing to log into multiple systems.