Restrict access to selected RCM Wiki resources

[cassgvp]

Summary Sentence

Some of the materials we would like to make accessible via the RCM team wiki should have access restricted to RCM team members only, to maintain appropriate data privacy and security.

Access to these materials can be managed in a number of ways. Pros and cons of each were discussed in RCM co-working 02/8/23. Summary of discussion points below

What needs to be done?

Which of the below (or other options you can think of!)

Github private repo list-of-links

Pro:

• Easy to control access al the repo level
• We have sole responsibility for that within the RCM team

Con:

• We'd have to create a new private repo (and github team). Having a private and public one could be difficult to manage.

Sharepoint list-of-links

Pro:

• We have sole responsibility for that within the RCM team - via RCM Group, which we control - ES: Easy. All at the same level of permissions
• This access restriction already exists, and we wouldn't have to create something new.
• Preference within Turing Professional Services teams.

Cons:

• Unfriendly and unpopular with users (could we make it pretty somehow? Suggestion to use MS Sway!)

Set permissions on each individual doc (across google and github)

Pro:

• Direct links could be maintained on the wiki (wouldn't have to click through two links)

Con:

• Would have to maintain access across many different places (not all of which we have sole management of). Risk of failure (e.g. someone not added/removed) is higher.

Who can help?

All RCMs!

Question: Are there any others pros or cons which should be considdered before making this descision?

Question: Do you agree that the appropriate solution is sharepoint?

---

Update after the issue was opened

Discussion about how we could make the distinction between what documents should be public and which should be private.

• Suggestion that all docs that are to be publicly accessable should be doi'd and licensed, with links to zenodo.
• Anything which is not doi'd and licenses should be access restricted.
• Question: Is it appropriate to put these zenodo entries in TTW zenodo community?

Discussion about how we generalise the resources and narative for TTW.

• We need something personal to our team, but the process could be generalisable.
• We want a narrative style, so it can be shared with stakeholders as a story of our community.
• Doesn't need to be long, e.g. 1 paragraph for every 6 months. Similar to briefing notes.