Home | Connectors | OpenText Content Storage Service | OpenText Content Storage Service - ArchivesSpace Integration and Automation
OpenText Content Storage Service provides secure, scalable cloud object storage for enterprise content, while ArchivesSpace is a widely used archives management platform for describing, managing, and providing access to archival collections. Together, they can support modern archival operations by separating metadata management from durable content storage, improving preservation, access, and operational control.
Data flow: ArchivesSpace to OpenText Content Storage Service
Archivists can maintain descriptive metadata, collection hierarchy, and access rules in ArchivesSpace while storing digitized manuscripts, photographs, audio, and video files in OpenText Content Storage Service. ArchivesSpace records can reference the storage location or object identifier in OpenText, allowing staff to manage large digital files without overloading the archival system.
Data flow: ArchivesSpace to OpenText Content Storage Service
Institutions can use ArchivesSpace to track archival descriptions and preservation status while storing preservation master files in OpenText Content Storage Service with retention policies, versioning, and lifecycle controls. This is useful for records that must remain immutable or available for long-term institutional memory and compliance requirements.
Data flow: OpenText Content Storage Service to ArchivesSpace
ArchivesSpace can expose collection descriptions and finding aids while linking users to access copies stored in OpenText Content Storage Service. This allows researchers, students, and internal users to retrieve files from a secure cloud repository without requiring the archival system to serve the content directly.
Data flow: External digitization workflow to OpenText Content Storage Service and ArchivesSpace
When archival materials are digitized, the integration can automatically store the files in OpenText Content Storage Service and create or update corresponding archival records in ArchivesSpace. Metadata such as title, date, creator, format, and rights can be synchronized from the ingest workflow into the archival description.
Data flow: Bi-directional
OpenText Content Storage Service can store preservation files and associated checksum values, while ArchivesSpace can maintain the descriptive and administrative metadata needed to track preservation actions. Periodic fixity checks in OpenText can trigger updates or alerts in ArchivesSpace when a file is verified, replaced, or flagged for review.
Data flow: ArchivesSpace to OpenText Content Storage Service
ArchivesSpace can manage collection-level or item-level access restrictions, while OpenText Content Storage Service enforces secure storage and controlled retrieval of the underlying files. This is especially valuable for sensitive records such as donor files, personnel records, legal materials, or culturally restricted content.
Data flow: Legacy repositories to OpenText Content Storage Service, then referenced in ArchivesSpace
Organizations migrating from shared drives, local servers, or aging digital repositories can move archival files into OpenText Content Storage Service and then update ArchivesSpace records to point to the new storage locations. This creates a more resilient and cloud-ready architecture while preserving the archival description layer.
Data flow: Bi-directional
ArchivesSpace can serve as the system of record for archival context, while OpenText Content Storage Service provides the governed storage layer. Archivists manage description and access decisions, IT manages storage policies and availability, and compliance teams review retention and disposition requirements using the same integrated content set.