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
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • 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
  • #25
Closed
Open
Created Nov 02, 2021 by Cassandra Gould van Praag@cassagOwner

Use common language for researchers working at different levels

Talking about data in terms of "raw" or "preprocessed" is not useful when the document is intended for researchers in different fields ("raw" means a different thing to a clinician vs. a physicist). The most appropriate suggestion we could agree on would be to discuss things in terms of file types, e.g. "k-space", "dicom", "nifti".

Assignee
Assign to
Time tracking