Globus

Globus is a robust data management platform designed to facilitate the secure and efficient transfer of large datasets across institutions and collaborators.

For a step-by step guide on how to login to Globus and transfer files, please see here.

Registering for a Globus Account

In order to make use of the Globus platform, you will need to create an account if you have not done so already. Most users will do so by using their institutional login (e.g., MIT Kerberos) by clicking the 'Log In' button in the top-right hand corner of the Globus website. After providing your consent, your new Globus account will be tied to your full name and email address as it appears at your institution.

If you are not affiliated with any of the organizations or research institutions listed, you can create your own unique login Globus login by filling out the Globus ID form. This login will take the form [e-mail], and will have its own login credentials associated with it.

Accessing KI Core Collections

If you are a core staff member and are looking for instructions on how to share data with collaborators via Globus, please see STEP 6 in this step-by-step guide.

There are several public guest collections available in Globus, through which you will be able to access generated core data:

1. Koch Institute Histology Data

2. Koch Institute Preclinical Imaging and Testing Data

3. Koch Institute Microscopy Data

4. Koch Institute Nano Data

5. Koch Institute BioMicro Data (BMC-PUB16)

6. Koch Institute BioMicro Data (BMC-PUB17)

Once you have created a Globus account, you can reach out to the core responsible for your data to request access to one of these collections, and a link will be shared with you via email after approval.

Until you are provided access, you will not be able to browse the collections via the links above.

Transfer Requests

If you require assistance with moving data to or from an external collaborator and local KI storage, we can help to facilitate that. This is the information that we'll need from you:

1. Whether the transfer is incoming or outgoing.

2. The volume (size, number of files) of data being moved.

3. What is the requested delivery date? This should be at least two weeks in advance in order to accommodate for network and filesystem performance.

Incoming Transfers

1. Where does the incoming data need to go (e.g., /net/bmc-lab2/...)?

2. Who will be needing access to write to the specified path? This can be a member of your team or your collaborator's team. For information on logging in to the Globus platform, please see above.

Outgoing Transfers

1. Which storage host is the outgoing data located on, and what is the absolute path to it (e.g., /net/bmc-lab2/...)? This will depend on your lab association.

2. Does the destination institution use Globus? If so, has the destination Globus collection been created yet? If not, the data can be transferred to local storage using Globus Connect Personal, which will need to be configured prior to the transfer.

3. Who will be needing access to read from the specified path? This can be a member of your team or your collaborator's team. For information on logging in to the Globus platform, please see above.

For additional assistance or questions, please reach out to [e-mail].

Resources

• https://docs.globus.org/guides/tutorials/manage-files/transfer-files/

• https://globus.stanford.edu/scenarios.html

• https://docs.globus.org/faq/security/

• https://docs.globus.org/faq/transfer-sharing/