UAB RCS managed Globus Collection creation process and schema

Endpoint

Mapped Collections

• Display Name
  • Scheme {institution} {department} RCS {platform}
  • Practically UAB RCS {platform}
  • Cheaha UAB IT RCS Cheaha (GPFS)
  • LTS UAB IT RCS Long-Term Storage (LTS)
  • Box UAB IT Enterprise Box
  • Blob UAB IT Enterprise Azure Blob
  • OneDrive UAB IT Enterprise Microsoft OneDrive
• Entity Type: derived from configuration
• Endpoint: derived from configuration
• Last Accessed: live information
• Domain ??
• Advertised Owner: CHECK
• Original Owner: CHECK
• Description: Furnish information
• Keywords:
  • hpc
  • htc
  • cheaha
  • cheaha.rc.uab.edu
  • rc.uab.edu
  • Descriptor List describing storage and relevant compute platform information
• User Message: |
  ...
  • Propagates to all Guest Collections
  • Ideas for content
    • Welcome message
    • Responsibilities, policies, expectations
    • Where to get support for Globus issues (support@listserv.uab.edu)
    • Where to get support for Data issues (from the collection owner)
• User Message Link: https://docs.rc.uab.edu/data/transfer/globus
  • Propagates to all Guest Collections
• Information Link: https://docs.rc.uab.edu/data/transfer/globus
• Contact Email: support@listserv.uab.edu
• Organization: University of Alabama at Birmingham
• Department: Information Technology - Research Computing (IT-RC)
• Other Contact Info: ??
• Visible To: derived from configuration
• Force Encryption: derived from configuration
• Subscription: derived from configuration
• Verified by: ??
• Authentication Timeout: derived from configuration
• Multi-factor authentication required: derived from configuration
• Max Permission Expiration: derived from configuration
• Restrict Transfers to High Assurance: ??
• UUID: automatically assigned

Start with the mapped-collection fields in this issue and review the linked Globus documentation at https://docs.rc.uab.edu/data/transfer/globus. Resolve the fields marked “??” or “CHECK” and define the managed collection creation process and schema. Done means the collection properties, derived values, messages, contacts, and verification requirements are documented.