Add guidance on what to do when PI leaves active students behind
Open
@wwarriner is already working on this.
Since May 2, 2025.
style: article/section 📝
system: identity-mgmt 🆔
- Dominant language
- Python
- Stars
- 24
- Forks
- 15
- Avg merge
- 10d 3h
- Merged PRs (30d)
- 1
Description
What would you like to see added?
On page: https://docs.rc.uab.edu/account_management/leaving_uab/
Ideas:
- If the student's PI made use of lab allocations, then the student can have more than 5 TB on those same platforms, but not necessarily the full lab amount. This ensures continuity for the student.
- If the student's PI had purchased additional storage hardware, then it should remain available to the student for the remainder of its service life, at the PI's discretion (I don't know what else they'd do with it).
- Because the student's situation is different than students whose PIs are at UAB, there is a case to be made that this is an equitable solution, if not an equal solution.
- This only applies to students and not to staff, faculty, or other PIs. I might even narrow it further to graduate students.
- The above would need to be on a case-by-case basis, because the exact needs of each student can be quite variable. We would need to ask them how much they can "whittle down" the data to just their needs.
- Directed to PIs: "before you leave, make sure you do X to support the on-going work of your students remaining at UAB"
- Directed to students: "if your PI is leaving..."
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.