Skip to content

Consider BIDS-compatibility / sidecar metadata. #7

@mslw

Description

@mslw

Overview:

  • BIDS specs for phenotypic and assessment data say that such data can be split into individual files (one per measurement tool, corresponding to our export_form), must be stored in a tsv file, may be accompanied by a json file describing columns in detail
  • redcap-to-bids, a Python 2 script, seems to do at least part of the task
  • REDCap API has an option to export metadata (data dictionary), and PyCap has an equivalent method. For an individual form, this outputs a sizeable json, which as far as I can see storesthe form definition. It doesn't match the BIDS one, but contains, among other, the field name and label (i.e. question text) for every question.

I don't have a formed assessment of how easy it would be to generate bids-like outputs. I leave two questions open:

  • should the extension aim to support BIDS formatting & sidecar generation?
  • if yes, should the sidecar be populated by the extension based on API queries, or should it be just a skeleton to be filled by users?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions