Questionnaire summary: Results from multiple choice questions

[harisood]

Summary of issue

Once the process for handling MCQs is decided (#11), we need to write reproducible code that allows us to get all the outputs from MCQs that can be used to open issues for the specification repo

    - 3) Admin control over data movement
    - 4) User authentication
    - 5) Network connectivity
    - 6. Ability to forbid copy and paste
    - 7. User experience
    - 8. Programming language support
    - 9. Enable users to install packages from selected external repositories (e.g. PyPI, CRAN, Conda, Maven)
    - 10. Commercially licenced software
    - 11. Containerisation
    - 12. Logging
    - 13. Automatic updates
    - 14. Compliance checking
    - 15. Automatic backup
    - 16. Customisable compute resources
    - 17. Additional compute beyond workspaces
    - 18. Collaborative/shared tools
    - 19. Limiting direct access to data/code
    - 20. Reproducible deployments
    - 23. Sensitivity tiering
    - 24. Which aspects of governance would it be important or useful to standardise

What needs to be done?

• Decide process (Questionnaire summary: Decide how to handle multiple choice Qs #11)
• Write a function that can reproducibly be applied generally across MCQs to get results
• Open issues for each category of question on the specification repo

Who can help?

@edwardchalstrey1 @harisood

Issue checklist

• I have assigned the appropriate work package label to this issue, and added any other relevant labels
• I have added this to the SATRE backlog (public) project board
• I have assigned this issue to at least one person on the SATRE team

[harisood]

@edwardchalstrey1 updated list above of all multiple choice questions. I think there should be an issue for each one, with their different aspects discussed in one place.

E.g. One issue for 'admin control over data movement', that then covers results from the three questions within in (ingress, egress, streaming ingress)

We also need to think how to incorporate results from related free text questions in #18 - e.g. the MCQ for how important programming language support is, and the free text laying out the languages a TRE should support

[edwardchalstrey1]

MCQ issues:

• [Change]: Questionnaire summary: Admin control over data movement satre-specification#50
• [Change]: Questionnaire summary: User authentication satre-specification#51
• [Discussion]: Questionnaire summary: Network connectivity satre-specification#52
• [Change]: Ability to forbid copy and paste satre-specification#53
• [Change]: Questionnaire summary: User experience satre-specification#54
• [Change]: Questionnaire summary: Programming language support satre-specification#55
• [Change]: Questionnaire summary: Enable users to install packages from selected external repositories (e.g. PyPI, CRAN, Conda, Maven) satre-specification#56
• [Discussion]: Questionnaire summary: Commercially licenced software satre-specification#57
• [Change]: Questionnaire summary: Containerisation satre-specification#58
• [Change]: Questionnaire summary: Logging satre-specification#59
• [Change]: Questionnaire summary: Automatic updates satre-specification#60
• [Change]: Questionnaire summary: Compliance checking satre-specification#61
• [Change]: Questionnaire summary: Automatic backup satre-specification#62
• [Change]: Questionnaire summary: Customisable compute resources satre-specification#63
• [Change]: Questionnaire summary: Additional compute beyond workspaces satre-specification#64
• [Change]: Questionnaire summary: Collaborative/shared tools satre-specification#65
• [Discussion]: Questionnaire summary: Limiting direct access to data/code satre-specification#66
• [Change]: Questionnaire summary: Reproducible deployments satre-specification#67
• [Change]: Questionnaire summary: Sensitivity tiering satre-specification#68
• [Change]: Questionnaire summary: Which aspects of governance would it be important or useful to standardise satre-specification#69