Help
Preservation Policy
Preservation Policy for OPUShtw
1. Objective and Purpose
The preservation policy of the OPUShtw repository describes the principles and procedures for securing, preserving and ensuring the long-term availability of the digital objects published on the platform. The aim is to guarantee the long-term accessibility, integrity and authenticity of the content.
2. Responsibilities & Duties
The OPUShtw repository is operated by the library of the Hochschule für Technik und Wirtschaft Berlin (HTW Berlin). The technical implementation is provided by the OPUS-Hosting service offered by the Kooperativen Bibliotheksverbund Berlin-Brandenburg (KOBV). The HTW Berlin University Library is a member of KOBV and uses its infrastructure to operate the repository. The content is provided by the submitting authors, editors and supervising institutions.
3. Data Backup and Protection against Data Loss
The hosting service guarantees protection against data loss through a multi-level backup concept:
- Daily incremental backups for all hosted instances
- Monthly full backups
- Backups are stored on two different tapes in a separately secured Lampertz IT secure room (SIN 21)
In the event of data loss (e.g. due to hardware defects or human error), the hosting service can restore the data to the desired status. Any data loss is limited to changes or publications made between two backups (max. 24 hours). These may need to be redone after the last backup has been restored.
4. Long-term Archiving
To ensure long-term availability and citability, all published documents are delivered to the archive system of the German National Library (DNB). This is where the actual long-term archiving takes place.
5. Integrity and Authenticity
Submitted objects are not altered after publication. Corrections or updates are posted as new versions and receive their own persistent identifiers. To ensure authenticity, the documents are provided with stable URLs and URNs.
6. Evaluation and Further Development
This Preservation Policy is reviewed regularly and if necessary, adapted to technical, legal or organisational developments.
Last updated: 03.09.2025

