Adam Li

Imo (not a strong opinion tho), 3) seems the most manageable and easiest solution. We should point to the relevant heudiconv documentation for going from: - dicoms -> BIDS imaging...

> to also be able to update `.tsv` files and not just `.json` files. So, would it make more sense to first invest some time to add `.tsv` support to...

I was thinking anything that was considered part of the metadata for the patient level. So for example, if I was working on subjects with some specified disease, then -...

@jasmainak I'm working on something in-house to deal w/ our needs, but yes agreed that it can become a bit uncertain how the API in a general-sense would look like....

> * After seeing the issues @sappelhoff ran into with annotations and `orig_time` and `first_samp` and all these weird interactions again (some recent MNE-Python PR), I don't think we should...

Just chiming in here with a random question I had related to mne-bids anonymizing: is it common to require age, handedness and sex to be scrubbed to be "anonymized"? I...

> maybe add just a new function in mne_bids to a posteriori remove age? I like the a-posteriori idea too FWIW because sometimes you write stuff to BIDS and then...

> let's not reinvent the wheel here. if we have a way to read it the events as a dataframe we can let users do what they want and then...

This would be a change to `electrodes/channels.tsv`. Say I need to change `description` of a channel, or set of channels to `resected`, or say `left temporal lobe`: ```Python new_vals =...

`BIDSPath` has `entities` property that can return the information as a dict