Warning emails that access to TRE is expiring#

You will be emailed reminders at approximately 90 days, 30 days and 1 day before your TRE access is due to end. Once the expiry date on your project passes, you will automatically be locked out of the TRE. You will no longer be able to access your project and all data files will be deleted six months after your project end date. This includes local representations of project views created by helper programs as well as intermediate/scratch files created during analyses. All documentation/syntax/codelists will be added to an archive folder and retained. Consider whether you anticipate requiring continued access to your project, e.g. if you plan to submit a manuscript and reviewers may require you to tweak or perform additional analyses. It is your responsibility to choose one of the two pathways listed below.

• PATHWAY 1: request an extension to your time in the TRE

• PATHWAY 2: wrap up your project.

1. Extend your TRE access#

If you need additional time to complete your research, you can submit an amendment via UK LLC Apply, UK LLC’s online application management system. See the Requesting an amendment guide. Please note that extending your time in the TRE does not affect your project data which remains static for the duration of the project unless a ‘new data’ amendment is submitted.

2. Wrap up your project#

1. Submit final file outs required for your publications or presentations. Please ensure you adhere to the rules detailed in the Publishing or presenting your research guide.

2. Collate all of your syntax, derived data and accompanying documentation in your project-specific GitLab.

3. Share your syntax with documentation for integration into the resource, by making a file-out request and ticking the box ‘GitHub/Gitlab sharing’. Approved files will be pushed to the shared subgroup in GitLab called ‘ReadAll’ - see Moving files in and out guide.

4. Push the approved syntax and documentation files to your project repository on the external public GitHub - see Using Git guide. You must set your UK LLC repository’s visibility to ‘Public’

5. Share your derived data outputs with documentation for integration into the resource by emailing the UK LLC Data Team at support@ukllc.ac.uk. Make sure you include the TRE file path of your data file(s) - see Using Git guide.