I am trying to come up with a BIDS structure for data that is both longitudinal and dyadic. Importantly, there is some behavioral data that is shared between members of a dyad, as discussed here. This approach uses the session entity to track dyads, but since my data is also longitudinal, I am already using the session entity to denote different time points. My current thought for hacking this is to use the acquisition entity for dyads as follows:
rawdata/ sub-S001/ ses-1/ sub-S001_ses-1_task-video_acq-dyad001_bold.nii.gz ses-2/ sub-S002/ ses-1/ sub-S002_ses-1_task-video_acq-dyad001_bold.nii.gz ses-2/ sub-S003/ ses-1/ sub-S003_ses-1_task-video_acq-dyad002_bold.nii.gz ses-2/ sourcedata/ beh/ acq-dyad001/ ses-1_task-conversation_acq-dyad001.m4a ses-2_task-conversation_acq-dyad001.m4a acq-dyad002/ ses-1_task-conversation_acq-dyad002.m4a ses-2_task-conversation_acq-dyad002.m4a
But if this is too flawed or there’s a better way to do it, I’d appreciate any feedback!