-
Notifications
You must be signed in to change notification settings - Fork 8
Expand file tree
/
Copy pathoffboarding.qmd
More file actions
46 lines (38 loc) · 1.98 KB
/
offboarding.qmd
File metadata and controls
46 lines (38 loc) · 1.98 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
Offboarding
================
With thanks to the [Bahlai lab](https://github.com/BahlaiLab) for the model and inspiration.
General project documentation
-----------------------------
* Make sure each of your projects complies with our [Data Management Plan](https://github.com/pinskylab/how_we_work/blob/master/data-management.md)
Data questions to consider
--------------------------
* Esnure each project follows the [Data Management Policy](https://github.com/pinskylab/how_we_work/blob/master/data-management.md)
* All data backed up in locations accessible to the lab and documented in associated GitHub repos
* All metadata complete and accessible from associated GitHub repos
* All scripts well documented and accessble from associated GitHub repos
* All other data been deleted from shared servers
Other
----
1. Turn in keys
1. Turn in computer or other equipment
1. Return books
Exit interview
--------------
Set up a time to talk with your mentor about:
1. What was the best part of being here?
1. What did you learn while you were here?
1. Did you get the support you needed, or could we have been better at it?
1. What can we improve for mentoring someone in your position in the future?
Write-up (for undergrads)
-------------------------
Write up a summary of your work with the following components:
1. Goals of the project
1. Methods
* detailed enough that someone could replicate your work
* explain any decisions you made and why
* link to and describe the input data for the project
* link to the project outputs
* include descriptions of metadata, any column headers in data sheets
1. Summary of findings
1. Potential next steps (could be a starting point for you at a later point or someone else)
The write-up can be a markdown document within your repository or a Google Doc. If you use a Google Doc, please link to it from the README within the repository, make sure the settings are such that anyone with the link can access it, and upload a saved pdf version to the repository.