Home | Connectors | OpenText Content Metadata Service - Dictionary | OpenText Content Metadata Service - Dictionary - OpenText File 360 Integration and Automation
Data flow: OpenText Content Metadata Service - Dictionary ? OpenText File 360
Use the centralized metadata dictionary to enforce consistent file classification in OpenText File 360, such as document type, business unit, retention category, project code, and confidentiality level. This ensures that shared files are tagged using approved values rather than free-text labels.
Business value: Improves search accuracy, reduces misclassification risk, and supports consistent governance across internal and external file exchanges.
Data flow: OpenText Content Metadata Service - Dictionary ? OpenText File 360
When teams create secure collaboration spaces in OpenText File 360, the metadata dictionary can supply standardized picklists for client name, engagement type, region, and document status. This is especially useful for legal, consulting, procurement, and account teams working with external parties.
Business value: Creates a common language across teams and partners, reducing errors in workspace setup and improving reporting on shared content.
Data flow: OpenText Content Metadata Service - Dictionary ? OpenText File 360
Use metadata definitions to support policy-based sharing rules in File 360. For example, files tagged as ?confidential,? ?regulated,? or ?board-level? can trigger stricter access controls, watermarking, or limited sharing options.
Business value: Strengthens compliance and reduces the chance of inappropriate file distribution while keeping collaboration efficient.
Data flow: OpenText File 360 ? OpenText Content Metadata Service - Dictionary
File 360 activity data and file attributes can be mapped back to the metadata model to support enterprise reporting on who shared what, with whom, under which business category, and for how long. This is useful for audits, legal discovery, and compliance reviews.
Business value: Improves traceability and makes it easier to produce reliable compliance reports across distributed file-sharing activity.
Data flow: Bi-directional
When a file?s business context changes in File 360, such as a project moving from active to closed, the updated metadata can be synchronized with the central dictionary model. In return, any changes to approved metadata values in the dictionary can be pushed to File 360 to keep file classification aligned with enterprise standards.
Business value: Keeps file-sharing content aligned with retention, archival, and disposition policies without manual rework.
Data flow: OpenText Content Metadata Service - Dictionary ? OpenText File 360
By applying the same metadata schema used across content platforms to files stored or shared in File 360, users can search by consistent attributes such as customer, matter, campaign, or record type. This is especially valuable for cross-functional teams that need to locate the latest approved version quickly.
Business value: Reduces time spent searching for files and improves reuse of approved content across departments.
Data flow: OpenText Content Metadata Service - Dictionary ? OpenText File 360
For supplier, client, or agency exchanges, the metadata dictionary can define required fields and allowed values before files are uploaded to File 360. This ensures external contributors submit content with the right business context, such as contract number, deliverable type, or approval stage.
Business value: Improves intake quality, reduces back-and-forth with external partners, and supports faster review and approval cycles.