Connecting to SDDS Globus (data on Lawrence) through Globus is only available to send/receive data to/from USD users at this time. If you are not from USD but working with someone who is, and wish to share data via Globus, please contact [email protected], and ask them to create a Globus collection with the data to be shared and then share that new collection with your Globus user. If you are from USD, and would like to share files with a non-USD user, please see the section Sharing with Other Users under the Adding Lawrence (Home and Lab Directories) section.
A collection consists of an endpoint which is connected to a directory on another system (Lawrence, a personal computer, etc.) and which is accessible through Globus. Think of it as a window, and the place on the system to which the endpoint is connected is a room. The endpoint (window) provides access through the internet to the part of the system or computer (room) it is attached to.
The base path of a collection is the location to which the collection connects.
For example, a base path:
would lead to Jane Smith's home directory, if Jane Smith's home directory was located at "/home/usd.local/jane.smith" on Lawrence.
Keep in mind that the base path shows the highest point in the file system of the destination computer that the Globus connection can reach. For example, a researcher using a collection with this base path:
will only be able to reach items in "folder2", not in the rest of Jane Smith's home directory.
Common options for collection base paths include:
- Individual home directories (on Lawrence)
- Lab directories (on Lawrence)
- SDDS lab
In regard to data on Lawrence, Guest collections allow a user to share data from locations on Lawrence that would normally be inaccessible to other users (e.g. a home directory, or a lab group directory if the guest is not a member of the lab group). Permissions on a guest collection can be set at read only (the guest can view, but not edit, the data), or read & write (the guest can view and edit data).
Sub-collections limit access to a particular directory and the sub-directories within it. For example: John Smith has a home directory that contains three sub-directories: 'Apples', 'Bananas', and 'Carrots'. Within the 'Carrots' sub-directory are files and a directory named 'Carrots-Location'.
John wants to share the 'Carrots' sub-directory, its files and the 'Carrots-Location' directory with a colleague, but not the 'Apples' or 'Bananas' directories. To do this, he can make a sub-collection for the 'Carrots' directory.
A personal endpoint connects Globus to a personal computer. Making a personal endpoint allows the user to access files and directories on the personal computer from Globus, and to transfer data from a personal computer to Lawrence, and vice versa, through Globus. This will likely be linked to your "My Documents" directory.
Groups allow an endpoint to be shared with the members of a collaboration/lab/etc., all at once, rather than sending invitations individually. When sharing with a group, access to the endpoint is dependent on membership to the group; if a member leaves the group, their access to the endpoint is forfeited.
Groups, therefore, are helpful in controlling access to an endpoint when there is high turnover in the collaboration of people who are using it.