Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • data-sharing-decision-tree data-sharing-decision-tree
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • open-science
  • community
  • data-sharing-decision-treedata-sharing-decision-tree
  • Issues
  • #19

Closed
Open
Created Aug 27, 2021 by Cassandra Gould van Praag@cassagOwner

[digram] Consider splitting the decision tree into levels relevant to each stakeholder

Prompted by Soft Launch 1, researchers wanted to have it clearly identified which activities were their responsibility and which were the responsibility of the PI. Suggested by @msouth, this could also be extended into all levels of stakeholder interest (ethics IRB, InfoSec, contracts... etc.).

Consider a method for drawing or visualising the diagram which makes it easy for different stakeholders to identify the processes which are relevant for them. This could be adding a symbol to each box to indicate who it applies to, or perhaps making them extendable (for example, "extend this box for the full researcher process"). Could alternatively mean redrawing with the detail only for that group.

Currently favouring a top level summary, which links to sub-processes. Need to think about what level of granularity for top level.

Edited Nov 02, 2021 by Cassandra Gould van Praag
Assignee
Assign to
Time tracking