Data archiving Clause Samples
A data archiving clause sets out the requirements and procedures for storing and preserving data over a specified period. It typically outlines what types of data must be archived, the format and security standards for storage, and the duration for which the data should be retained. For example, it may require that all project-related documents be securely stored for seven years after project completion. The core function of this clause is to ensure that important information is preserved for future reference, compliance, or audit purposes, thereby reducing the risk of data loss or regulatory breaches.
Data archiving. 7.1 Subject to the pre-existing obligations above, storage of data is the responsibility of the User/Institution to whom it belongs. Unless the Instruct-▇▇▇▇ Centre explicitly offers a data archive service, Users are responsible for copying and making arrangements for the long term storage of the Experimental data. In this latter case the facility will collect and maintain an accountable proof of the transfer of the data to the user, for verification purposes.
7.2 Subject to future developments in the context of the European Open Science Cloud (EOSC) and of the approval of the appropriate Instruct-▇▇▇▇ internal protocols of actions, and if in the future the EOSC initiative will provide the opportunity to store all, or a subset, of the experimental data acquired at Instruct-▇▇▇▇ Centres in the course of Instruct-▇▇▇▇ Access projects, then Instruct-▇▇▇▇ will implement the necessary actions to take full advantage of such an opportunity. These data will be appropriately labelled using, for instance, Digital Object Identifiers (DOI).
Data archiving. As noted above, hydroacoustic surveys typically produce several hundred megabytes of data and so a substantial and robust data archiving system is essential. The safe storage of such data is essential not only in order to allow analyses to be repeated with contemporary software using variations in analytical parameters, but also to allow them to be revisited with future developments in analytical software which may allow their analysis in new ways. In addition, unless read into dedicated playback or analysis software which can be cumbersome when large volumes of files are being managed, raw data files are largely uninformative other than perhaps the date and time of their collection being incorporated into the file name. Consequently, archived raw data files should be accompanied by metadata files. The latter can be as simple as spreadsheets, or as complex as a relational database or geographic information system.
Data archiving. It is advised that original data will be archived on a hard disk (on a laptop/desktop PC) at the partner’s institution. The lead researcher in charge will make additional backup copies of the data at least once a week on a remote hard disk. This remote hard disk then will be kept in a secure area (possibly outside the laboratory – for data redundancy reasons). Processed data is also to be uploaded to the FTP site (see section 6.5.1), which will act as an additional back-up and system to share information between the partners.
Data archiving. The use case is about implementing data archiving for raw data from experiments to an external facility and the restore of the data. STFC38 has worked in this use case, both as a provider of storage to be used for archiving (ECHO Storage at STFC) and for investigating solutions to perform efficient backup. Initially the Rucio39 and FTS40 services have been evaluated in order to move data from ILL as a facility selected as pilot. Both services are available in the EOSC portal41, 42and offered by STFC as a provider. In order to use Rucio and FTS, there has been the need to install a gridftp server on the ILL facility as the data transfer is implemented only between storage endpoints. After the initial tests, the archive solution via Rucio has been discarded due to the need to ingest datasets inside the Rucio database which is a requirement to perform the data archiving operations. The usage of rclone43 has then been piloted, given that the storage at STFC offers also an S3 interface which is easily accessible via that tool. The pilot via rclone has given successful results in terms of usability and performance, and the amount of data archived at STFC storage has reached 200 TB.
Data archiving. All SIEM data compressed and a SHA1 hash of each archive is stored in the platform database for data integrity purposes.
Data archiving. The Collaboration Board shall elaborate in due time a data archiving strategy and long term data access, evaluate its cost and will propose to the Financial Board its implementation.
Data archiving. Hubspan reserves the right to archive certain data beginning 60 days after transaction date. Hubspan Service Level Agreement This Service Level Agreement provides definitions used throughout the document, defines Priority Levels relative to Technical Support, and includes details relative to Technical Support Services. In addition, this document defines exclusions to Hubspan’s Service.