This section expands upon the previous section on Basic Globus transfers. It is still an introductory level of content, but may not apply to all use cases.

Discussed in this section are the transfer options in Globus, sharing data with others, and then briefly touch on the Globus CLI and flows functionality.

Globus Transfer Options

Beyond simply transferring data, Globus enables users optional features that enhance the functionality of data transfers. Here are a few that ARCC frequently uses:

• Label - Because Globus keeps a record of each transfer along with the stats bout them, it can be hard to determine which transfer is which based solely on the transfer ID and date. Giving a transfer a human-readable label can help users keep track of each transfer.

• Sync - to only transfer new or changed files. Selecting this option gives the ability to choose how files will be overwritten on the destination file system. The options for syncing can be where the modification time of a file is newer, the file size is different, the file on the source does not exist on the destination, or where the checksum is different. When using this option, ARCC recommends using the checksum option, to cover a vareity of scenarios

• Preserve source file modification times - After transfer of a file, the modification time on the destination will reflect the modification time on the source instead of the time the transfer completed.

Transfer Option Example

Straight Code - No context

Limit to 16 lines in the example. 














This is the end

Same Thing With Images

Alternatively No Table

Finally The End