Restrict image modalities to those we support

[surchs]

At the moment, anything that is a BIDS suffix will be treated as a imaging modality. It might make more sense for us to have a list of allowable modalities that we support and only encode these.

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed.

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed.

[alyssadai]

For the sake of clarifying the issue, is this not the current list of "allowed" modalities we support?

bagel-cli/bagel/mappings.py

Lines 10 to 22 in 4da00b6

	BIDS = {
	"anat": NIDM.pf + ":Anatomical",
	"func": NIDM.pf + ":Functional",
	"dwi": NIDM.pf + ":DiffusionWeighted",
	"bval": NIDM.pf + ":b-value",
	"bvec": NIDM.pf + ":b-vector",
	"T1w": NIDM.pf + ":T1Weighted",
	"T2w": NIDM.pf + ":T2Weighted",
	"inplaneT2": NIDM.pf + ":T2Weighted",
	"bold": NIDM.pf + ":FlowWeighted",
	"dti": NIDM.pf + ":DiffusionTensor",
	"asl": NIDM.pf + ":ArterialSpinLabeling",
	}

I believe there are other types we don't currently include, e.g., EEG. Do you know of a 'master list' of BIDS suffixes somewhere in the docs that could act as a reference?

[surchs]

Ah yeah, good point, this probably needs some clarification. afaik BIDS has data types: https://bids-specification.readthedocs.io/en/stable/common-principles.html#definitions and suffixes: e.g. https://bids-specification.readthedocs.io/en/stable/modality-specific-files/magnetic-resonance-imaging-data.html#non-parametric-structural-mr-images

So there are two things to clarify:

• what does "support" mean, because I don't see a reason we couldn't have EEG data
• we should probably differentiate data types from suffixes

[github-actions]

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

• prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
• close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
• archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
  apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
  label in the future. Use sparingly!