(arrange_data_ingress)=

# Arrange data ingress with data provider

> This task is the responsibility of {ref}`role_project_team`.

## Background

There are a number of things we need to confirm, both internally and with the [Data Provider Representative (DPR)](https://data-safe-haven.readthedocs.io/en/v4.2.2/roles/data_provider_representative/index.html), in order to safely ingress data.
This includes the contact details for the person who will ingress data from the data provider, what the data includes and how and when ingress will take place.
This then needs to be signed off by the DPR, and the {ref}`role_tresa` operations and deployment representatives before actioning.

## Process

It's very important to read the rest of this document carefully and ensure all relevant steps of the process are carried out:

### Adding a record to the ROPA

> TODO: add a link to the ROPA document

Before progressing with data ingress, the ingress method, contact and contents must be validated and, if the project will work with or generate personal data, be added to our organisational Record of Processing Activities (ROPA).

If the project is working with, or will generate, personal data, it must be added to our ROPA.
All projects with a TRE on the ROPA should be recorded on the `REG` tab. Find some time with the Data Protection team to add this record to the ROPA.

### TRE Data Ingress Process Form

1. In your SharePoint folder, go to `data ingress -> Turing TRE Data Ingress Process`

2. Fill in the required project details:

   - **Project name:** The name of your project
   - **Data Ingress contact name:** The name of the person who will perform data ingress. This is likely to be the DPR, though they may have nominated somebody else.
   - **Data Ingress contact email:** The email of the person who will perform data ingress. This is likely to be the DPR, though they may have nominated somebody else.
   - **Data Ingress contact IP:** (Optional) If ingress will happen by `Temporary write-only upload token`, the public IP address of the person who will perform data ingress. This is likely to be the DPR, though they may have nominated somebody else.

3. Fill in the required data ingress details:

   - **Summary of data for ingress:** An overview of the nature and contents of the data to be ingressed. This is needed so we can confirm the correct data is in the environment once ingress has taken place.
   - **Method of ingress**: Our preferred method of ingress is {ref}`perform_data_ingress_ase`. However we understand this may not be possible for certain data providers. If this is not possible, please refer to {ref}`perform_data_ingress` to see other possible methods of ingress, have a conversation with the {ref}`role_tresa` to determine the best method for ingress, and record it here.
   - **Intended date of data ingress:** The date on which, or date window during which, ingress is planned.
   - **Additional information required for ingress:** Any additional information required for ingress. This may be especially required if the method of ingress is different than usual. If no further information is required write `N/A` or `None`.

4. Share the TRE Data Ingress Process Form to sign via DocuSign with the DPR, and both {ref}`role_tresa` operations and deployment representatives by emailing [trustedresearch@turing.ac.uk](mailto:trustedresearch@turing.ac.uk)

5. Add the signed document to the SharePoint folder `data ingress -> signed`

### Supporting Documents

Please upload any useful supporting documents, for instance Data Sharing Agreements, to the folder `data-ingress -> Supporting documents`.

### NHS patient data

If the project is working with NHS patient data, evidence that [the data provider is opt-out compliant](https://digital.nhs.uk/services/national-data-opt-out) must be in the `data-ingress -> Supporting documents` folder.