Data ingress#
Purpose#
Data must be brought into the Turing TRE in order to carry out research. Some projects may also require other artifacts, such as code. The purpose of this document is to define the security procedures around data ingress.
Scope#
This procedure covers all data and code ingress for all projects running in the Turing TRE.
Responsibilities#
Role |
Responsibility |
---|---|
Confirming that data ingress has been successfully completed |
|
Making data ingress request |
|
Assessing whether requested artifacts are appropriate for ingress |
|
Assisting external data providers in uploading data to the TRE |
Procedure#
Complete data ingress form
Responsible: 🧑🏫 Project data manager
Fill out a Turing TRE Data Ingress Request form using the template in the
folderFollow the guidance here
Note that several methods of bringing data into the TRE are possible, discuss which is most appropriate with the data provider:
Adding a record to the ROPA
Responsible: 🧑💻 Trusted research data manager
If the project will work with or generate personal data it must be added to the Turing Record of Processing Activities (ROPA).
Work with the Data Protection team to ensure this is recorded correctly.
Review ingress request
Responsible: 🧑💻 Trusted research data manager
Review the
Turing TRE Data Ingress Request
form and any supporting documents.If any changes are needed, discuss these with the 🧑🔬 Project team and amend the form accordingly.
Approve data ingress
Send the form to be DocuSigned by each of the appropriate responsible people named on the project initiation form
Place the signed form in the
folder in Sharepoint
Carry out data ingress
🧑🔧 Trusted research system administrator: Work with the data provider and help them carry out the data ingress
Validate data ingress
🧑🔬 Project team: Validate that the ingressed data is complete and correct.