OpenText Core Content - Metadata - OpenText Information Archive Integration and Automation

Common Integration Use Cases Between OpenText Core Content - Metadata and OpenText Information Archive

• Metadata-driven archiving of finalized content

  Direction: OpenText Core Content - Metadata to OpenText Information Archive

  When content in OpenText Core Content reaches a final or inactive state, metadata such as document type, retention class, business unit, and legal hold status can be passed to OpenText Information Archive to determine archive location, retention period, and disposition rules. This helps content owners apply consistent retention policies without manual review, reducing compliance risk and storage costs.

• Retention classification based on governed metadata

  Direction: OpenText Core Content - Metadata to OpenText Information Archive

  Controlled vocabularies and validation rules in OpenText Core Content - Metadata can standardize key archive attributes before records are transferred. OpenText Information Archive can then use those validated values to assign retention schedules, legal holds, and destruction dates. This is especially useful for regulated industries where archive accuracy depends on consistent metadata quality.

• Legacy system decommissioning with metadata preservation

  Direction: OpenText Information Archive to OpenText Core Content - Metadata

  When legacy applications are retired, their historical documents and records can be moved into OpenText Information Archive while preserving business metadata such as customer ID, case number, product code, and transaction date. Selected metadata can also be synchronized into OpenText Core Content - Metadata to support search, reporting, and downstream content workflows. This enables business users to find archived records without accessing the old system.

• Unified search across active and archived content

  Direction: Bi-directional

  OpenText Core Content - Metadata can provide the classification structure for active content, while OpenText Information Archive stores long-term records. By aligning metadata fields and values across both platforms, users can search active and archived content using the same business terms, such as client name, project code, or retention category. This improves information access for legal, audit, and operations teams.

• Automated disposition of content after archive transfer

  Direction: OpenText Core Content - Metadata to OpenText Information Archive

  Once content is archived and retention obligations are confirmed in OpenText Information Archive, status updates can be returned to OpenText Core Content - Metadata to mark the source content as archived, superseded, or eligible for deletion. This supports clean-up of working repositories and prevents duplicate retention of the same record in multiple systems.

• Compliance reporting with standardized metadata

  Direction: Bi-directional

  OpenText Core Content - Metadata can enforce the business taxonomy used to classify content, while OpenText Information Archive can store the authoritative record copy and retention history. Together, they support audit reporting on what was archived, when it was archived, who classified it, and which retention rule applies. This is valuable for legal discovery, regulatory audits, and internal controls.

• Project and case file lifecycle management

  Direction: OpenText Core Content - Metadata to OpenText Information Archive

  For project-based or case-based work, metadata can identify when a file is closed, the responsible department, and the required retention period. Closed files can then be transferred to OpenText Information Archive for long-term preservation, while OpenText Core Content retains only active working files. This reduces clutter in operational repositories and improves team productivity.