preservazione a lungo termine

As explained in the introductory page, IA2 provides storage space for"Data Sharing"and for"Long-Term Preservation." The latter refers to saving data to a). Quest’ultima si riferisce al salvataggio dei dati su libreria a nastro (works).

How the Tape Libraryworks)
How to Request an Account
How to Write a Data Management Plan (DMP)

The Data Management Plan must provide all relevant information for proper data preservation in accordance with FAIR principles.

You can follow these guidelines to write your DMP:

Required long-term storage space and technical justification:

How much space do you need and why? What is the scientific and technical motivation for the requested storage space? Remember that once data is written to the Tape Library, it cannot be deleted or modified. Therefore, ensure you truly want to archive and preserve it—meaning it is not data that, however large, can easily be regenerated or simply lacks value. It may be that only a subset of your data requires long-term preservation, rather than all of it. Consider the cost of regenerating the data versus the feasibility of preserving it in a long-term archive.

Data type, format, and structure of the collection:

What type of data do you want to archive (e.g., simulations, observations, etc.), in which file formats (e.g., FITS, HDF5, TAR, etc.), and how large are these files? Are they compressed? How are the data and corresponding metadata structured? How are data and metadata organized across files and folders? Provide any information helpful for understanding the type of data and metadata you want to archive and how they are organized.

Expected access frequency:

How often will the data be accessed? Both in terms of how much data will be consulted or downloaded at one time, and the frequency of access over time. You may differentiate by data type, as some data may be accessed more frequently than others.

Accesspolicy):

Who will have access to the data? Only the account contact person or a group of individuals? Do we need to account for restrictive access authorization rules?

Do you plan to make your data public?

Is it possible that the data is private now, but may be made available for public access in the future? If your data is strictly private-access, answer "No". Otherwise, provide any useful information on how you plan to make your data public according to FAIR principles. Which target community will it serve if made public? Will all data be public, or only a subset? Is there a funding plan to support this activity?

Additional information:

Provide any additional information you consider useful or necessary to help us best preserve your data.

How to PerformData Ingestion)
  1. Once the account is created, the user will be assigned a scratch area where they can transfer their data;
  2. Transfers can be performed via scp or rsync. Any additional software must be agreed upon directly with the IA2 team;
  3. Once the user completes the transfer of a data block (a directory with subdirectories), it will be taken over (upon user notification) and frozen;
  4. We kindly ask you to prepare and structure data in directories containing no more than 2,000 units, or keep in mind that leaf directories with more than 2,000 files will be converted into .tar files during the archiving procedure. A Bash script can be used to run a check on the files prior to uploading. For each directory, please generate a file listing the computed checksums for its files to verify file integrity. Please leave each checksum file inside its corresponding directory.
Executing the Checksum Script

Before starting this process, verify that files or directories do not contain special characters such as:

[ ] < > ? \ / " : | ' *`

Assuming your data is located in /home//:

Place the script in /home/ and execute it after modifying execution permissions:

Bash
cd /home/
chmod +x checksum
bash checksum my_data &

This script will run in the background and generate a log file. To check the execution status of the script, use:

Bash
pgrep -f checksum

Once the data is saved to tape, it can be managed by the user in read-only mode.

DataRetrieval)

Data stored on tape can be retrieved via VOSpace. From the VOSpace interface, users can trigger an asynchronous recall (async-recall) for both individual files and folders. Once recalled, download links will appear on the VOSpace interface.

In all cases, the user must initiate an asynchronous recall (async-recall) of the data to download it. Requested data will be placed in the user's directory while preserving the original path structure.

FAQ