This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
onboarding_affiliates [2016/11/02 17:51] jmbanda [How to connect to DB1] |
onboarding_affiliates [2021/11/23 17:25] (current) acallaha |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Onboarding for affiliates ====== | ====== Onboarding for affiliates ====== | ||
- | ===== Onboarding steps ===== | ||
- | - Get SUNET ID to access the Stanford network. External collaborators will require sponsorship from a Stanford staff. | ||
- | - Get access to our [[int: | ||
- | - Identify the [[int: | ||
- | - Complete the necessary training | ||
- | - IF you will access db1 AND dev1, you need to complete the following training: | ||
- | - Protecting Patient Privacy - contact Shauna Cruz (shaunalc@stanford.edu) to get signed up via LawRoom | ||
- | - Protection of Human Subjects - GROUP 1: IRB REQUIRED FOR MEDICAL RESEARCH INVESTIGATORS AND STAFF - done via {{https:// | ||
- | - IF you will access ONLY db1, you need to complete the following training: | ||
- | - HIPAA Certification for Workforce Members who Do Not Work with PHI - contact Shauna Cruz (shaunalc@stanford.edu) to get signed up via LawRoom | ||
- | - Upload your certificates at: http:// | ||
- | - Understand our [[int: | ||
- | - You are encouraged to set up a wiki page to document your project. [[int: | ||
- | - For details regarding specific steps, schedule a one-on-one session with the relevant person | ||
- | * Server access: Alex Skrenchuk | ||
- | * Data use agreement: Nigam Shah | ||
- | * Text processing: Juan Banda | ||
- | * Cohort building: | ||
- | * [[int: | ||
- | * Patient matching | ||
- | * Data analysis: | ||
- | ===== Data sharing and Use Agreement ===== | + | See the sections on ' |
- | + | ||
- | * Use of the data will be restricted | + | |
- | + | ||
- | * All participants and users of data have completed CITI training, | + | |
- | + | ||
- | * __No copies of the data__ will leave Stanford BMIR servers. If it does, collaboration is over. | + | |
- | + | ||
- | * All __publications or presentations__ relating to the data will be cleared | + | |
- | + | ||
- | ===== How to connect to Dev2 ====== | + | |
- | If you are off-campus (or on the wireless network), you will need [[https://itservices.stanford.edu/ | + | |
- | Not to be confused with DB1, this only needs a simple SSH command to connect (open a terminal): | + | |
- | + | ||
- | < | + | |
- | + | ||
- | The first time you do this it will ask you to store the RSA key, just type yes. After the first time, this should not appear anymore. | + | |
- | + | ||
- | ===== How to connect to DB1 ====== | + | |
- | There are multiple different ways of connecting to the database server. If you are off-campus, you will need [[https:// | + | |
- | + | ||
- | **NOTE: Your DB1 password is NOT the same as your dev2 password. It is found on the .my.cnf file file on your home/ | + | |
- | + | ||
- | 1) (The easiest way) Set up a MySQL GUI:\\ | + | |
- | There are plenty of options to use, but we recommend: | + | |
- | - (MAC) Sequel Pro has built-in SSH tunneling: http:// | + | |
- | - (PC) MySQL Workbench, DB Visualizer | + | |
- | - (Linux) MySQL Workbench | + | |
- | Example: setting up MySQL workbench with tunneling\\ | + | |
- | {{: | + | |
- | + | ||
- | 2) (Second easiest way) From the command line :\\ | + | |
- | + | ||
- | - SSH to [[http://shahlab.stanford.edu/onboarding_affiliates?& | + | |
- | - Use Mysql: < | + | |
- | + | ||
- | 3) (hard and confusing) Create a tunnel from the database server to your computer: | + | |
- | + | ||
- | - To connect to // | + | |
- | < | + | |
- | - Use your local copy of MySQL (you need to instal the MySQL client on your computer) \\ | + | |
- | - Then connect to the database of interest | + | |
- | < | + |