+ "text": "Offboarding\nWhen leaving VU Amsterdam, you are likely to leave behind project-related data. This data needs to be archived and be accessible for other researchers for verification of research data. This is also an important step in complying with regulations of funding organisations. If data are no longer being used in ongoing research, have been archived or published, and can be removed from active storage (i.e. Research Drive and the active storage part of Yoda), you can ask functional application management in the University Library to remove these data for you. There is a request form in which you can indicate what data it concerns.\nResearchers who remain at VU Amsterdam may want to use your (archived/published) data in the future. To facilitate this, we provide a template to fill out that can be handed over to your manager. Additionally, for removing data, it is important that you make clear which data can be removed, if this has not been arranged through the request form linked above. If this is not done, it remains unclear to your department/manager whether the data can be removed in accordance with agreements with research funders (e.g., Dutch Research Council, NWO) and privacy laws (e.g., General Data Protection Regulation, GDPR).\nNote: this is a general template and the process may vary from department to department. Therefore, we recommend that you check with your department if any department-specific workflows are in place.\n\nContact Information\n\n\n\nField\nDetails\n\n\n\n\nName\n\n\n\nNew email\n\n\n\nVUNETID\n\n\n\n\n\n\nImportant Data\n\nDataset/Software #1\n\n\n\n\n\n\n\nField\nDetails\n\n\n\n\nTitle of dataset/software (if applicable)\n\n\n\nDescription (can point to existing metadata). Think about structure, hierarchy etc.\n\n\n\nLocation (e.g., URL, SciStor, Yoda)\n\n\n\nSoftware to read data\n\n\n\nFuture contact(s) (e.g., you, someone else at VU)\n\n\n\nLicence\n\n\n\nPrivacy issues (if any)\n\n\n\nOther (e.g., password protection, special storage instructions, data co-ownership)\n\n\n\n\n\n\nDataset/Software #2\n\n\n\n\n\n\n\nField\nDetails\n\n\n\n\nTitle of dataset/software (if applicable)\n\n\n\nDescription (can point to existing metadata). Think about structure, hierarchy etc.\n\n\n\nLocation (e.g., URL, SciStor, Yoda)\n\n\n\nSoftware to read data\n\n\n\nFuture contact(s) (e.g., you, someone else at VU)\n\n\n\nLicence\n\n\n\nPrivacy issues (if any)\n\n\n\nOther (e.g., password protection, special storage instructions, data co-ownership)\n\n\n\n\nNOTE: In case you have more datasets, please copy the table above as many times as needed.\n\n\n\nData Removal\nI declare that all important data was archived (see above), and my account and associated data can be removed on the following platforms:\n\nSciStor\nSURFdrive\nResearch Drive\nYoda Active storage\nOneDrive\nLab journals\nOther, namely ….\n\nArchiving data is a relatively long-term solution, but even archived data has a lifespan (e.g., Yoda data will be removed after 10 years by default). What should happen when data is due for removal from the archiving platform?\n\nData can be removed.\nA decision on further archiving can be made by:\n\nName:\nPosition:\nDepartment and faculty:\nEmail:\n\n\nDate, and location:\nSignature:"
0 commit comments