Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider BIDS-compatibility / sidecar metadata. #7

Open
mslw opened this issue Jan 30, 2023 · 0 comments
Open

Consider BIDS-compatibility / sidecar metadata. #7

mslw opened this issue Jan 30, 2023 · 0 comments

Comments

@mslw
Copy link
Collaborator

mslw commented Jan 30, 2023

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?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant