Home | Connectors | Box | Box - OpenText Content Metadata Service Integration and Automation
Flow: Box ? OpenText Content Metadata Service
When users upload contracts, patient records, policy documents, or financial files into Box, the content is sent to OpenText Content Metadata Service to apply a standardized metadata model such as document type, business unit, retention class, jurisdiction, and sensitivity level. The enriched metadata is then returned or synchronized back to Box to support consistent classification and governance.
Business value: Improves search accuracy, supports compliance, and reduces manual tagging errors across distributed teams.
Flow: Box ? OpenText Content Metadata Service
Box content can be classified using metadata rules managed centrally in OpenText Content Metadata Service. For example, legal, HR, and finance documents can be assigned retention categories and review dates based on a shared metadata schema. Box Governance can then use those classifications to enforce retention and disposition policies.
Business value: Creates consistent records management across departments and reduces compliance risk from misclassified content.
Flow: Bi-directional
Organizations using both platforms can maintain a single metadata model in OpenText Content Metadata Service and apply it to content stored in Box. This enables users to search for documents using the same business terms and filters across repositories, such as client name, project code, case number, or contract status.
Business value: Speeds up document retrieval, improves user productivity, and reduces duplicate content creation caused by poor discoverability.
Flow: Box ? OpenText Content Metadata Service ? Box Relay or external workflow tools
Documents uploaded to Box can be enriched with metadata from OpenText Content Metadata Service and then routed into the correct approval or review workflow. For example, an NDA tagged as ?high risk? or ?external counterparty? can be automatically sent for legal review, while a standard vendor agreement can follow a faster approval path.
Business value: Reduces cycle times, improves routing accuracy, and ensures the right stakeholders review the right content.
Flow: OpenText Content Metadata Service ? Box
Organizations that share content with external partners through Box can use OpenText Content Metadata Service to enforce approved metadata structures before files are shared. This ensures that partner-facing documents carry the correct labels for confidentiality, region, project, and version control, even when content is exchanged across organizational boundaries.
Business value: Improves control over shared content, supports secure collaboration, and reduces the risk of inconsistent document labeling.
Flow: Bi-directional
In enterprises that use Box for collaboration and OpenText Core Content for core records or repository-based content, OpenText Content Metadata Service can act as the central metadata layer. Box content and OpenText-managed content can both reference the same metadata definitions, making it easier to manage content lifecycle, reporting, and compliance across platforms.
Business value: Eliminates metadata silos, supports enterprise-wide reporting, and simplifies governance across multiple content systems.
Flow: Box ? OpenText Content Metadata Service
Compliance teams can use metadata enrichment to add audit-relevant attributes to content stored in Box, such as matter ID, regulatory category, evidence type, and review status. This makes it easier to prepare for audits, legal holds, and investigations by ensuring content is consistently labeled and traceable.
Business value: Strengthens audit readiness, improves defensibility, and reduces time spent assembling evidence for reviews or investigations.