The Vendor is required to provide hosted digital preservation storage software and services.
- Provide a digital preservation software/service solution to provide long-term preservation and ongoing accessibility for digital records.
- Current digital storage solution is utilizing both agency servers with replicated cloud storage and cloud storage.
- This digital storage stores a wide variety of file types and formats - including but not limited to audio, video, images, documents, PDF, email, and websites.
- The awarded digital preservation software/system will be agency digital storage solution to provide long term preservation and access to digital government records.
- A “Digital Preservation System” or “DPS” refers to an OAIS-aligned system that combines a management platform (software as a service) and a preservation storage environment (storage as a service) in order to support the full lifecycle of digital content, including ingest, management, preservation, and access over time.
- Currently, DPL manages and preserves digital content using a combination of locally managed storage and cloud services, and a set of largely open-source tools that provide digital preservation functions such as virus checking, disk imaging, file characterization, fixity verification, and metadata extraction.
- Management documentation (including checksums, manifests, and PREMIS metadata) is largely stored as XML, TXT, and PDF files in managed storage.
- Access and discovery is limited to DPL Archives Services and Technical Services staff, who may view access copies. Preservation copies are marked in folders as “locked.”
- Preservation copies may be examined only through the file view software program Quick View Plus.
- Public access to files is by appointment only. Copies of files are loaded on a thaw space accessible to a patron access computer (PAC) in the archives reading room.
- Researchers use the viewing software Quick View Plus and are able to take screenshots or download PDFs of the digital content through the software.
- Functional Requirements
• Ensure integrity and authenticity through checksums, scheduled fixity checking, automated repair from replicated copies, and full audit logging with preservation metadata (e.g., PREMIS).
• Support complex digital objects with persistent identifiers and preservation of structure, versions, and relationships between components.
• Provide system independence and exit options by storing content in application-independent structures, supporting batch export of content and metadata, and enabling software escrow.
• Enable secure, scalable ingest with virus checking, quarantine, retention of bit streams and essential context (structure, timestamps, documentation, metadata), and ingest reporting with issue flagging.
• Deliver comprehensive file format identification and characterization including format/version identification, technical metadata extraction, render ability checks, and validation against specifications.
• Provide resilient storage and continuity via multi-location replication, regular backups, tested restore processes, and management reporting.
• Record and document preservation actions and their outcomes in preservation metadata.
• Enforce governance and security controls including protection against deletion or tampering and role-based access controls.
• Support controlled access and discovery with a public interface, restricted-access options (e.g., on-site only), exposure of authenticity information, and harvestable metadata/content.
- System include:
• The system should enable preservation actions that fulfil preservation plans designed to mitigate identified preservation risks.
• The system must support replication and storage management. The system must have the ability to store multiple copies of ingested digital content on different storage systems in different geographical locations.
• The system must enable authentic digital content and metadata to be ingested.
• The system must precisely record and manage the integrity and authenticity of the digital content and metadata it holds. It must use checksums to verify that digital content has not accidentally or maliciously been changed over time and metadata to record any actions enacted on the content.
• The system must support the management of digital content and metadata over time.
• The system must enable the controlled discovery of, and access to, digital content and metadata.
Set up free email alerts and get notified when new government bids, tenders and procurement opportunities match your industry and location. Choose daily or weekly delivery.