Table of Contents
UVA CS Collaborator Accounts
Definitions
A UVA Computer Science (CS) Collaborator account is a standard access account that enables an external collaborator from another institution to utilize CS department compute resources for collaborative work.
Purpose
CS collaborator accounts are used for when a student, faculty, or researcher from another institution requires access to resources contained within the UVA CS department’s computing environment.
Procedure & Requirements
Obtaining a CS Collaborator Account
- A UVA Sponsored account must be obtained through UVA Information Technology Systems (ITS) to obtain a valid and unique UVA computing ID
- Link to ITS' page for UVA sponsored accounts: https://in.virginia.edu/sponsor
- Once a UVA account has been issued along with a computing ID, a CS collaborator account can then be created. To do so, submit a request to cshelpdesk@virginia.edu including the following information
- The name of the sponsored user
- The sponsored user’s institution
- The expected duration of the collaborator account
- Access requirements
- Which systems or servers the collaborator will log into or which specific department resources will be needed
- Project directory access (if applicable)
- Level of access on servers (sudo requirements if applicable)
CS Collaborator Account Cleanup
UVA CS collaborator accounts adhere to the standard account cleanup procedure of the department. After the specified end-date for maintaining the account has passed, the account will be disabled, and the user’s home directory will be purged after one month after being disabled, with or without warning.
CS Collaborator Account Renewal
The sponsor of the UVA CS collaborator account is responsible for contacting the CS IT helpdesk to initialize a renewal request to extend the end-date of the account.
Recommendations
- For CS Collaborator accounts, it is recommended that important data (code, results, etc.) not be kept within the collaborator’s home directory or any volatile/scratch storage space such as /bigtemp. Instead, such data should be moved to a project directory if persistent storage is required.