Hey everyone,
There is a open pull request that might change a bit how the specification will look: [MISC] Add mini entity tables after filename templates by tsalo · Pull Request #781 · bids-standard/bids-specification · GitHub
In practice a mini table would be added below each template for the filenames, to list all the possible entities for that data type and mention if that entity is required or not.
Pro:
It is reusing some of the tables that already exist in the appendix, but adds them next to each filename template.
Con:
It adds cluttering sometimes with small tables: see here.
https://bids-specification--781.org.readthedocs.build/en/781/04-modality-specific-files/03-electroencephalography.html#eeg-recording-data
And sometimes big tables: see here
https://bids-specification--781.org.readthedocs.build/en/781/04-modality-specific-files/01-magnetic-resonance-imaging-data.html#anatomy-imaging-data
The maintainers would be curious to hear the thoughts of the “users” of the BIDS specification, regarding if this kind of visual / structure change to the spec would be welcome or would add more confusion. Feel free to chime in the pull request: [MISC] Add mini entity tables after filename templates by tsalo · Pull Request #781 · bids-standard/bids-specification · GitHub
@+
Rémi
1 Like
Hi!
I’m not 100% clear on what you mean by “users” of the BIDS specifications, but as a current BEP coordinator, I consider myself a “user”… So here are my thoughs 
Overall, I find this addition very useful! It provides a “quick overview” of the filename template which has a real added value (instead of having to go through a lot of text, you just look at the table and you know what’s up )…
Obviously, when the table is small, the added value is clear; when the table is big (like the anat example), it becomes too big to still be quickly readable, but anyhow, the persons who needs it can grab the info, e.g by looking at the single line that is of interest to them… Worst case scenario, people will ignore it…
Bottomline for me: either it’s clearly useful, or it’s less clear but doesn’t hurt… So if you average the level of usefulness across modalities, I think it remains strictly positive, so I’d be in favor of accepting this addition!
1 Like
Hey Sylvain
yeah I think you definitely qualify as a user.
several people on the mailing list raised concern that the added clutter would not be worth it, so not sure about this yet.
another possibility would be a single sentence below the filename templates that link to the appendix: would be less in your face and still somewhat make this information available.
Hello BIDS community,
This post seems resolved but it also seems to best for my comment:
How can I get/download a simple table-format of the Entity Table?
Formatting in the pdf version of the specs is hard to read and seems wrong (note the “Format” line) below.
The layout of the Entity Table in the browsable version of the specs is also hard to read as one (me using firefox) has to scroll down the table the access the horizontal slider.
Just a csv or something like that would do it for me, and I guess a link in the specs to such downloadable table would do it for many.
For now, if someone could share such simple format Entity Table here, that would be awesome!
Thanks for your attention and
Have a very good day!
Sebastien
Its not beautiful but can go straight to the source for entity requirement per suffix:
1 Like
