Skip to content

offboarding.md

Latest commit

 

History

History
57 lines (20 loc) · 2.71 KB

offboarding.md

File metadata and controls

57 lines (20 loc) · 2.71 KB

Offboarding

Congratulations! You have reached the end of your time here in the Dallas lab. This does not mean we have to be done collaborating by any means. This document mainly sreves just to make sure that there is a plan in place to make sure everyone in the lab still has access to data, code, and hardware resources that you worked on while in the lab, and also that you have continued access to data and code (don't want anything to get lost!). You will stay on the lab GitHub account, so no worries about not having access to any of your existing repositories.

Graduation

We have two sets of regalia (one medium and one XL, I think?) so you won't need to worry about that. The Graduate School will probably email you with questions about name pronounciation and other bits. Otherwise, this is a simple procedure of sitting most of the time, standing part of the time, and at some point I put a silly looking hood on you and shake your hand. Then we'll probably have some cookies or a beer in the lab to celebrate your accomplishment.

Logistics

4 weeks before leaving

  • start backing up any data/code you want to have access to on your own hard drives (if you need a flash drive or external hd, I think we can help with that). I can install a clean version of Ubuntu on the machine, but it will wipe off all of the existing data, so be sure that everything you want comes off that machine.

  • be sure you have all forms filled out with Graduate School and any departmental hoops jumped.

  • let me know if you want to take any experimental animals or anything with you and we can arrange any of that.

2 weeks before leaving

  • start transferring emails from the university email over to a gmail or another email account. Essentially plan to lose access to your university email account fairly quickly.

  • clean up any leftover experiments. Anything still running, make sure someone is taking care of it, knows the experimental protocol, and can handle it.

  • if you are in charge of an experimental system, make sure that someone is ready to take it over or that it is able to be easily paused. All protocols for the system should be in their own GitHub repository and should be clearly written so that anyone could follow them and care for experimental animals.

1 weeks before leaving

  • label lab notebooks on their spine and the front with your name and the dates that correspond to the entries contained within. Take scans of any pages you want persistent access to.

  • return any lab-owned books you have laying around.

0 weeks before leaving

  • return all hardware that is lab-owned, so flash drives, computers, equipment, etc.

  • return lab keys to Kelly (CLS 401)

  • say your farewells!