Consider how we want to store session / directory paths for different types of data

[alyssadai]

Currently, the session column in the participant results TSV is named SessionFilePath, but this is a bit misleading since

• it only contains paths to the raw imaging data for a session
• it is a path to a directory, not a file

At some point, we will want to store a path to the derivative data for a session as well, based on the Nipoppy structure. We should decide whether each of these data types should live in a different column, and more informative names for them.

[surchs]

@alyssadai mind adding a bit more context on what raised the question for you, before we forget

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