Data manager onboarding#

Trusted research data managers are responsible for monitoring the service area activities and keep records up to date. Start by following the Onboarding.

Monitor the TRESA email inbox#

You should be able to access trustedresearch@turing.ac.uk and respond to emails from project teams and others. Most requests will relate to one of the tasks, but there could be requests from new projects wishing to set up a TRE.

This inbox will receive automated emails for Azure Subscriptions set up for TREs from the Research Computing Platforms (RCP) team, for example when a subscription is running low on credits. See Track budget.

Keep the project boards updated#

The SRE project board is accessible at https://github.com/orgs/alan-turing-institute/projects/25/views/1?layout=board and contains issues that have been created via the TRE deployment issue template (see the .github folder in the trusted research repo), with one issue per SRE (and SHM).

For each new project, an issue will be opened during project initiation. As the TRESA lead, you should ensure that at least one member of TRESA is assigned to (and therefore responsible for) each of these issues and tracks the progress through the project lifecycle by checking the boxes that relate to the tasks as they go.

The management project board is accessible at https://github.com/orgs/alan-turing-institute/projects/52/views/1?layout=board and is a place for general issues for the service area.

Coordinate with project teams#

Make sure the project teams for each active SRE are aware of this documentation and link them to pages as appropriate. It’s the job of TRESA to track the project lifecycle, but many of the individual tasks will need to be carried out by the 🧑‍🔬 Project team. Where time is critical for any given task, TRESA should send email reminders to the project team representative(s).

Make sure training is up to date#

Ensure that everyone in the centralised record of all users has up-to-date training.

Important

Note that this includes all members of the Trusted Research team and DSH developers as well as regular research users.

More details are available in the training monitoring process <process_monitor_training> documentation.