This is a custom Confluence template that is intended to be re-used in the creation of workshops presented by ARCC on the Wiki. All of the content in these sections is intended to be replaced by the author of the workshop. The first step in this style guide is to ensure that the the page is in wide mode to maximize the real estate for content when possible. The Title of the Page should be the same as the Title of the workshop and this section should include a quick intro to the topic, why it’s important for ARCC users, and what users should expect to get out of this workshop. Next should be a Table of Contents macro in vertical format. The Table is intended to be used as an agenda section for presenter mode as well as navigation for non-presenting viewing so that users can find the documentation and navigate to what they need to brush up on. Finally, at the end of each section, there should be a divider to indicate the separation of “slides”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.

...

Headers and Sections

...

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.

...

Code Examples

Please use the "code snippet" in the + button when creating code examples. Also please do not go
past the width of the table. This is to prevent scroll bars appearing













This is the Max number of code lines to show on an example

...