Switch to handling only .tsv input files (to align with other neurobagel tools)

[alyssadai]

One thing to consider is that CSV is probably still a more common file format for phenotypic (and even other types of) tabular data than TSV, generally speaking. Not sure, however if this is a good enough reason to keep it.

Steps to implement

• update functions handling input file loading
• update upload buttons
• convert existing example bagel files to .tsv (both pheno + imaging)
• update error messages, docstrings, comments

[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]

@michellewang, any thoughts? I think @nikhil153 is neutral on this issue - not sure if you have an intuition about whether a switch to TSV could reduce usability for generic users.

[michellewang]

I don't have a preference either -- TSVs can be loaded/saved in Excel etc. so usability shouldn't be greatly reduced compared to CSV in my opinion. And with the ongoing Nipoppy refactor it shouldn't be too hard to make the switch from CSV to TSVs