You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
with current master 0.2.0-11-gb3d8897 (and new reworked metadata handling in revolution 0.9.0-183-g8765949, pybids seems to be 0.8.0) saw that side car files have only datalad_core extractor records:
ideally they should carry bids extractor metadata such as subject/session/task. Didn't look into it, i.e. either it is something on pybids or our side to do to address it
The text was updated successfully, but these errors were encountered:
Why would you would like to see that? Those are metadata. They describe subject/session/task, but they are not itself part of the data that makes up subject/session/task.
Those are files potentially needed to get "full" set of (meta)data for a specific subject/session. So, e.g. if I am interested "give me files for subject X", I would like to see .json and .tsv and ... whatnot which is relevant to analysis of this subject. If I am interested in particular type of file(s), then extension and whatever other metadata fields could be used to restrict the query. I really see no reason why sidecar files shouldn't be annotated with metadata on where they belong (in terms of subject/session)
I dont see how this should be done for a semantic markup, please make a proposal.
That being said, I think we will end up with separate extractors for metadata dumps (like the current bids and nifti1) extractors, and extractors for linked data. What you want is easily done in the former.
with current master 0.2.0-11-gb3d8897 (and new reworked metadata handling in revolution 0.9.0-183-g8765949, pybids seems to be 0.8.0) saw that side car files have only
datalad_core
extractor records:ideally they should carry bids extractor metadata such as subject/session/task. Didn't look into it, i.e. either it is something on pybids or our side to do to address it
The text was updated successfully, but these errors were encountered: