Data Transfer Federation & File Transfer Service

Link to the service

Logo

Detailed description of the service

The Data Transfer Federation allows researchers to access and transfer data between different storage systems using their home organization’s user account, based on their access rights to the resources in a collaborative project. The storage systems in a federation are either dedicated large-scale systems or systems associated with High-Performance Computing (HPC).

The data transfer federation is based on FTS3 developed by Cern.

Apart from the offer to transfer files, the service also considers organizational aspects to allow high volume data transferring between sites.

Terms of use & restrictions

Service is still in early development. TOU are not defined, yet.

Contact

Mozhdeh Farhadi, mozhdeh.farhadi@kit.edu

References

publications that reference (or report on using) the service

#WhyNFDI

Service is still in early development.

Miscellaneous

Service is still in early development. The service is based on FTS3 (https://github.com/cern-fts/fts3).

Tags

NFDI4ING services may be relevant to different users according to varying requirements. To support filtering or sorting, we added a tag system outlining which archetype, phase of the data lifecycle, or degree of maturity a service corresponds to. By clicking on one of the tags below, you can get an overview of all services aligned with each tag.

This service has the following tags:

Alex, Betty, Caden, Doris, Ellen, Fiona, IRL2, Service, Storing & Computing

The tags correspond to:
The Archetypes: Services relevant to Alex – Bespoke Experiments, Betty – Research Software Engineering, Caden – Provenance Tracking, Doris – High Performance Computing, Ellen – Complex Systems, Fiona – Data Re-Use and Enrichment

The data lifecycle: Services related to Informing & Planning, Organising & Processing, Describing & Documenting, Storing & Computing,
Finding & Re-Using, Learning & Teaching

The maturity of the service: Services sorted according to their maturity and status of their integration into the larger NFDI service landscape. For this we use the Integration Readiness Level (IRL), ranging from IRL0 (no specifications, strictly internal use) up to IRL4 (fully integrated in the German research data landscape and the EOSC). Click here for a diagram outlining all Integration Readiness Levels.