FIXMETA(1)

💅 FIXMETA(1) — bestie edition 💅

Generated Python Manual ✨ ok so listen up, this is fixmeta(1) and she is that girl 🎀

---

✨ NAME ✨

fixmeta — the little bidsapp that goes in and ✨fixes✨ your metadata. no cap.

---

🌸 SYNOPSIS 🌸

fixmeta [-h] [-p LABEL [LABEL ...]] [-b NAME] bidsfolder pattern metadata

---

🦋 DESCRIPTION 🦋

Okay so, fixmeta is a bidsapp that can change or add metadata in BIDS data repositories. Like, it literally goes into your BIDS folder and edits the metadata for you. obsessed. 💖

And bestie, the glow-up doesn't stop there — the fixmeta app supports the use of special bidsmap features, such as dynamic values to use source data attributes or properties, or to populate IntendedFor and B0FieldIdentifier/B0FieldSource values. iykyk 👑

the three little arguments that run the whole show 🫶

• bidsfolder — The BIDS root directory that needs fixing. and yes bestie, this happens in place 😭 so it's not making a cute little copy somewhere, it's editing the real thing. be brave.
• pattern — A globlike recursive search pattern (relative to the subject/session folder) that selects the json sidecar targets that need to be fixed, e.g. '*task-*echo-1*'. so like, it's the vibe check for which files get touched 💅
• metadata — A dictionary with key-value pairs of the metadata that needs to be fixed. Here's the tea on how it behaves, and this part matters:
  • If the value is a string, then this metadata is written to the sidecars as is. simple, no drama, periodt.
  • But if it's a list of old/new strings, i.e. [old1, new1, old2, new2, ..], then the existing metadata is re-written, with all occurrences of the substring old replaced by new. it's giving find-and-replace but make it metadata 🎀

---

💅 OPTIONS 💅

• -p LABEL [LABEL ...], --participant LABEL [LABEL ...] — A space separated list of sub-# identifiers to be processed (the sub- prefix can be left out, you're welcome 💖). If not specified then all participants will be processed. she's thorough like that.
• -b NAME, --bidsmap NAME — Selects a custom study bidsmap file for extracting source data properties and attributes. If the bidsmap filename is just the base name (i.e. no "/" in the name) then it is assumed to be located in the current directory or in bidsfolder/code/bidscoin. Default: bidsmap.yaml or else the template bidsmap. ✨

---

🙈 COMMENTS 🙈

okay bestie here are the examples, and honestly they ate 🔥 look at these:

fixmeta myproject/bids func/*task-reward1* '{"TaskName": "Monetary reward paradigm 1"}'
fixmeta myproject/bids *acq-reward1* '{"B0FieldIdentifier": ["<<", "_", ">>", ""], "B0FieldSource": ["<<", "_", ">>", ""]}'
fixmeta myproject/bids fmap/*run-2* '{"IntendedFor": "<<task/*run-2*_bold*>>"}' -p 001 003

like look at that third one — selecting fmap/*run-2*, populating IntendedFor, and only doing participants 001 and 003. main character energy fr fr 👑

---

👑 AUTHOR 👑

Marcel Zwiers <m.zwiers@donders.ru.nl> — ty for your service legend 🫶

---

and that's the whole page, bestie!! this was bidscoin 4.6.2 generated on 2025-11-06 💖 go fix that metadata, you got this, mwah 😘✨