Automatic update of protocol_translator when adding new sourcedata?

[hippocampo]

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

BIDSKIT works great and I am very happy with this incredibly helpful tool! I work with heterogenous clinical datasets from multiple scanners; each DCM2NIIx conversion produces unique titles to their protocols. I've found that once I run bidskit (1st and 2nd pass) successfully, if I then add new sourcedata it is not "seen" or updated in the protocol_translator file. If I delete the protocol_translator file and re-run bidskit, I have to re-do the whole protocol translator again.

Describe the solution you'd like A clear and concise description of what you want to happen.

Is there anyway to make the protocol_translator a dynamic file such that I can keep re-running bidskit after entering new sourcedata? Thank you!

[jmtyszka]

@hippocampo Glad you're finding bidskit useful! Making the protocol translator dynamically updatable is a great idea and I'll implement it as soon as I can. Stay tuned.