Policies Affecting Our Role in Secure Research
Non-Networked Machines
In partnership with the Secure Data Archive, SSCS provides End-User-Device support to SSD researchers. Our objectives are both to facilitate research and comply with the technical specifications and restrictions mandated by data providers. While these restrictions are often unique to individual data providers, within the SSCS team we have worked to come up with procedures which ensure we can provide support quickly and effectively.
- Software Changes
- SSCS will work with researchers to first install all needed software prior to the introduction of secure data. This will minimize the amount of delay between installations of packages on non-networked devices.
- Prior to the introduction of secure data, researchers should provide test data to ensure software packages are up-to-date.
- Adding/Removing Users
- When requesting the addition or removal of users from a secure data system governed by a DUA, SSCS will require documentation that the Data Provider has been informed of the change and approved it.
- SSCS requests the following information:
- URA DUA# from UChicago URA
- Data Provider’s License ID or other contract Identifier
- IRB protocol #
- Uchicago PI
- Acceptable Documentation
- PI or research team should supply a PDF of the amended DUA
- Where access is governed by an online portal without a ‘paper trail’ SSCS will accept screen shots.
- [how to take a screen shot]
- Once Accepted, SSCS will initiate the change and update the ticket with confirmation.
- SSCS requests the following information:
- Relocating Computers
-
-
- When relocating a system, SSCS will depend on accurate documentation of the change from the data provider and research team
-
-
- When requesting the addition or removal of users from a secure data system governed by a DUA, SSCS will require documentation that the Data Provider has been informed of the change and approved it.