OpenText Core Content - Metadata - Preservica Integration and Automation

Common Integration Use Cases Between OpenText Core Content - Metadata and Preservica

1. Transfer governed metadata from OpenText Core Content to Preservica for long-term digital preservation

Data flow: OpenText Core Content - Metadata ? Preservica

Organizations can push approved metadata schemas, controlled values, and validation rules from OpenText Core Content into Preservica when content is selected for archival preservation. This ensures that records, digital assets, and compliance documents retain consistent descriptive, administrative, and retention metadata as they move into the preservation environment.

Business value: Reduces metadata loss during handoff, improves discoverability in the archive, and supports compliance with retention and records management policies.

2. Synchronize archival classification metadata back to OpenText Core Content for operational visibility

Data flow: Preservica ? OpenText Core Content - Metadata

Preservica can return preservation-specific metadata such as archive identifiers, retention status, fixity checks, legal hold indicators, and preservation events back into OpenText Core Content. Business users working in the content platform can then see which assets have been archived, preserved, or placed under retention controls without needing to access the archive separately.

Business value: Improves transparency for legal, compliance, and content operations teams while reducing duplicate tracking in spreadsheets or manual logs.

3. Automate archival packaging based on metadata rules in OpenText Core Content

Data flow: OpenText Core Content - Metadata ? Preservica

When content reaches a defined lifecycle stage in OpenText Core Content, metadata rules can trigger automated packaging and transfer to Preservica. For example, records tagged as ?closed case,? ?final version,? or ?regulatory submission? can be routed with the correct metadata set, folder structure, and retention category for archival ingest.

Business value: Eliminates manual archive preparation, speeds up records transfer, and ensures only approved content is preserved with the right context.

4. Enforce metadata quality before content is accepted into preservation workflows

Data flow: OpenText Core Content - Metadata ? Preservica

OpenText Core Content can act as the metadata governance layer that validates required fields before content is eligible for transfer to Preservica. Missing author, date, department, record class, or sensitivity labels can block transfer until corrected, ensuring preservation packages are complete and compliant.

Business value: Prevents incomplete archival records, reduces remediation effort later, and supports audit-ready preservation processes.

5. Support legal hold and e-discovery workflows with synchronized metadata

Data flow: Bi-directional

When legal teams place content on hold in OpenText Core Content, the hold status and related case metadata can be sent to Preservica to prevent disposal or alteration of preserved records. In return, Preservica can provide preservation evidence and chain-of-custody metadata back to OpenText Core Content for legal review and reporting.

Business value: Strengthens defensibility in litigation, improves chain-of-custody visibility, and reduces risk of accidental deletion or policy conflicts.

6. Improve enterprise search and reporting across active and archived content

Data flow: Preservica ? OpenText Core Content - Metadata

Preservation metadata from Preservica can be indexed or mapped into OpenText Core Content to give business users a unified view of active and archived assets. Teams can search by archive status, retention period, subject category, or preservation event without switching systems.

Business value: Enhances content findability, supports reporting across the full content lifecycle, and reduces time spent locating archived records.

7. Maintain consistent metadata governance across records, archives, and regulated content

Data flow: Bi-directional

Enterprises can use OpenText Core Content as the authoritative source for controlled vocabularies, taxonomy updates, and metadata standards, then propagate those standards to Preservica. Preservica can return preservation-specific extensions that are mapped back into OpenText Core Content so both systems remain aligned over time.

Business value: Ensures metadata consistency across departments, simplifies governance, and reduces the risk of conflicting classifications between operational and archival repositories.

8. Enable lifecycle-based retention and disposition decisions with preservation context

Data flow: Preservica ? OpenText Core Content - Metadata

Preservica can provide retention milestones, preservation actions, and disposition eligibility back to OpenText Core Content so records managers can make informed lifecycle decisions. This is especially useful for regulated industries where archival status affects whether content can be destroyed, retained, or reviewed for extended preservation.

Business value: Supports compliant disposition, improves retention governance, and helps records teams make decisions based on authoritative preservation data.