Priority till end of 2021/beginning of 2022 | |
RDP-over-https (before end of 2021) | No more downloading the RDP file, no more stepping stone to access Linux VMs, directly access your VMs securely in your browser. |
URL-whitelisting | Initially it will be through a ticket request, but yes GitHub etc will then be a possibility. |
Software Share per Tenant | Your Support Team can maintain a repo of common used software packages that reduce the effort and time to download locally, and upload before you can install it. |
Audit V2.0 | Right now, we do extensive logging but we want to make it more user friendly and compliant. |
API-management | First step to allow 3rd party developers to directly interact with some of the features of myDRE. One of the first APIs allows central repositories to upload directly data to a Workspace. |
Multi-region support | The ability for an organization to store and process data in a different Microsoft Azure region; UK, Switzerland, etc. Some of the larger consortia might like this. However, Workspace to Workspace transfers between Regions will not be supported at first. This because we need to build an extra step to ensure easy demonstrable compliance. |
UX/UI redesign | This will speedup some of the development, reduce the learning curve for new users and new functionalities, and should provide a nicer experience in general. Speed-over-fanciness, but we'll use the improvement in fanciness to improve the speed. |
Start the ISO 27001 certification | This will be of great help, also to you, for there is plenty of time we have spent the last couple of weeks on several grants answering ISO27001 and GDPR related questions. |
In the research, it is crucial to report the exact steps followed in order for others to be able to reproduce the study. The same can be applied for reporting a bug in DRE. Sometimes the issue is very complex but often the problem can be solved with just a few simple tricks and checks.
We all know that encountering errors and bugs can be frustrating and annoying. Troubleshooting a reported bug can be equally frustrating and time-consuming if it isn’t clear what the exact issue is. Therefore, it is important to clearly state the reproduction steps to recreate the error that emerged. This helps to identify where the problem lies, what went wrong, and what should be fixed.
Information that could be very helpful for us:
· Include a description where you shortly explain why goes wrong
· Include steps to reproduce as accurately as possible
· Include screenshots and images of the problem, this always helps
· Mention when the problem started? Did anything change?
· Mention any relevant information such as browser user, workspace name, VM name, username, log in via institution/own computer