HIC is always looking to the future of TREs to better support good research practices and user experience. We’ll try and track some of these larger ideas below.
Feature | Description |
|---|---|
Semi-Automated Egress Checking | When an output request is submitted, it is added to a queue for manual checking. Extending this pipeline to support arbitrary automated checks, such as scanning for specific values such as PROCHI, could drastically improve the speed and efficiency our output checking workflow. |
Inter-Project Egress Workflows | Transferring files (mainly scripts) between projects is already something we are happy to do, but via the standard file egress mechanism, followed by releasing those checked files to the project. We could automate the release of these files to a specific project specified at egress submission. |
Code Repositories (e.g. Git) Diode | We’d like to support the automated ingress of code from Git repositories, allowing the shifting of development and testing outside of the TRE. This could also include the potential for an egress-like mechanism for pushing changes back to the external repository after some checks have been performed. |
With all of these there will be caveats which need further investigation and understanding, such as intellectual property and information governance.