Bids-specification: add optional fields to some of the JSONs

Created on 31 Jul 2020  Â·  5Comments  Â·  Source: bids-standard/bids-specification

Some suggestions for some optional fields that could be added in json files.

The idea is that some of those data should (must?) be provided in the papers we write (cf COBIDAS) so it could make sense if they were included in the dataset metadata.

dataset_description.json

  • URL to pre-registration
  • Information about eventual statistical power analysis

~- Financial grants info~
~- ethics: information about the IRB that approved for the data acquisition~

Add in json files related to task files

  • for all modality with tasks (func, eeg, meg, ieeg)

    • Presentation software used

    • OS

    • Software

    • Version

    • URL to code of that was run to present the software

  • for task fMRI

    • if some design efficiency optimization

Let me know how you feel. If there is some enthusiasm for some of those I could open separate PRs to keep things and discussions modular.

All 5 comments

thanks for the suggestions @Remi-Gau

I particularly like OS, software, Version, Url for better descriptions of tasks.

Information about eventual statistical power analysis

could you go into a bit more detail and perhaps provide an example of what you would think such a field would look like?

Just to mention. The current BIDS specification of dataset-description has
Funding and EthicsApprovals fields. However, the EthicsApprovals field was
not in the JSON schema in the bids-validator. Hence pull request bids-standard/bids-validator#1031 to
the bids-validator, which was just merged.

On Sun, Aug 2, 2020 at 5:46 AM Stefan Appelhoff notifications@github.com
wrote:

thanks for the suggestions @Remi-Gau https://github.com/Remi-Gau

I particularly like OS, software, Version, Url for better descriptions of
tasks.

Information about eventual statistical power analysis

could you go into a bit more detail and perhaps provide an example of what
you would think such a field would look like?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bids-standard/bids-specification/issues/552#issuecomment-667657999,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJCJOSQCBEN4EHHVOBCKTTR6U7ZTANCNFSM4PP7K4OQ
.

@VisLab yup I did see your PR which made me realize I was out of date on that front. :smile:

I crossed out the things that are already in the specs in my initial message.

thanks for the suggestions @Remi-Gau

I particularly like OS, software, Version, Url for better descriptions of tasks.

Information about eventual statistical power analysis

could you go into a bit more detail and perhaps provide an example of what you would think such a field would look like?

Will open separate issues for both of those

I am closing this now, because @Remi-Gau started tracking the two proposals in two distinct issues with a distinct PR each (I love it :+1: ) thanks Remi!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

franklin-feingold picture franklin-feingold  Â·  8Comments

effigies picture effigies  Â·  6Comments

Lestropie picture Lestropie  Â·  10Comments

tsalo picture tsalo  Â·  9Comments

Remi-Gau picture Remi-Gau  Â·  4Comments