Redesign data transfer

[geoffreyweal]

This pull request will focus on resigning the data transfer page as well as create a best practices page.

[gemini-code-assist]

Summary of Changes

Hello @geoffreyweal, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request undertakes a comprehensive redesign of the data transfer documentation, specifically focusing on Globus. The primary goal is to enhance the user experience by providing a more intuitive, structured, and up-to-date set of guides. This involves creating new, focused pages for key tasks and concepts, consolidating related information, and removing outdated content, ultimately making it easier for users to understand and utilize Globus for file transfers.

Highlights

• Documentation Restructuring: The Globus data transfer documentation has been completely reorganized for improved clarity and user experience, with a new navigation structure.
• New Comprehensive Guides: Several new dedicated pages have been added covering essential topics such as first-time Globus setup, adding personal computers as endpoints, transferring data between personal endpoints, managing bookmarks, sharing collections, and utilizing the Globus Command Line Interface (CLI).
• Consolidated Data Transfer Instructions: The main Data_Transfer_using_Globus.md file has been significantly rewritten to provide a streamlined, step-by-step guide for GUI-based transfers, now incorporating Globus restrictions and a comprehensive table of New Zealand Data Transfer Nodes (DTNs).
• Removal of Redundant/Outdated Content: Numerous older, less focused, or redundant documentation files related to Globus quick start, endpoint activation, path allocation, initial sign-up, and personal endpoint configuration have been removed to reduce clutter and ensure information is current and concise.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

---

Data flows with grace, Through networks, fast and wide, Knowledge finds its place.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

Test deployment available at https://callumwalley.github.io/mkdocs-demo-deploy/nesi/support-docs/Redesign-Data-Transfer

Seems the following pages differ;

• Data_Transfer_Best_Practices
• Data_Transfer_Using_MobaXterm
• Data_Transfer_Using_WinSCP
• FileSender
• File_Managers
• Add_Your_Computer_To_Globus
• Bookmarks
• Data_Transfer_Between_Personal_Endpoints
• Data_Transfer_using_Globus
• First_Time_Setup
• Globus_CLI
• Overview
• Share_Collections
• Syncing_files_with_globus_automate
• Introduction
• OnDemand
• RClone
• Rsync
• VSCode
• scp
• Data_Transfer_using_Globus
• Data_transfer_without_additional_authentication_credentials
• Globus_Paths-Permissions-Storage_Allocation
• Globus_Quick_Start_Guide
• Globus_endpoint_activation
• Initial_Globus_Sign_Up-and_your_Globus_Identities
• National_Data_Transfer_Platform
• Personal_Globus_Endpoint_Configuration
• Re_creating_Shared_Collections_and_Bookmarks_in_Globus
• Moving_files_to_and_from_the_cluster
• Git_Bash_Windows
• MobaXterm_Setup_Windows
• Standard_Terminal_Setup
• WinSCP-PuTTY_Setup_Windows
• Storage_best_practices
• index

See all deployed demo sites