q02/phantom-mri-bids
9
1
Fork 0
Code Issues 12 Pull requests Projects Releases Packages Wiki Activity Actions

Aachen: Build Q01 DICOM (super) dataset #12

New issue
Open
opened 2025-10-18 11:57:27 +00:00 by mih · 0 comments
mih commented 2025-10-18 11:57:27 +00:00
Owner
Copy link

This dataset will track all dataset of individual scan sessions by means of subdatasets. The is going to be one subdataset per session.

The super dataset could be made (consortium) public to allow for tracking acquisition progress, as along as the tracked sudatasets do not have a BIF subject identifier in their name or location URL.

This can be achieved when pseudonymizing the DataLad dataset location and name -- likely using a subject's Q01 code. This pseudonymization does not effect DICOM organization or naming. It is strictly limited to the DataLad realm.

Here is a suggestion for a possible organization within the DataLad superdataset:

sub-A0001/
  ses-01/ -> subdataset (repository) via URL that does not include BIF identifier
  ses-02/ ....
  ...
sub-A0001/
  ...
...

where A0001 is an Aachen-specific subject pseudocode, as described in the TRR379 SOP.

When a new scan was completed:

  1. A session subdataset is created, and deposited (see #10).
  2. The subdataset is registered in the superdataset under subject pseudocode and session number (integer increment)
  3. The DICOM superdataset is updated at its (consortium) public hosting location for members to become aware of the progress and to trigger potential CI runs.

Data protection details

Due to the nature of subdataset handling in DataLad, this superdataset will only contain the following information on a DICOM session subdataset:

  • URL of the location of the DataLad subdataset (not the location of the DICOMs!)
  • anonymous GITSHA identifier of the subdataset version
  • anonymous UUID identifier of the subdataset
This dataset will track all dataset of individual scan sessions by means of subdatasets. The is going to be one subdataset per session. The super dataset could be made (consortium) public to allow for tracking acquisition progress, as along as the tracked sudatasets do not have a BIF subject identifier in their name or location URL. This can be achieved when pseudonymizing the DataLad dataset location and name -- likely using a subject's Q01 code. This pseudonymization does not effect DICOM organization or naming. It is strictly limited to the DataLad realm. Here is a suggestion for a possible organization within the DataLad superdataset: ``` sub-A0001/ ses-01/ -> subdataset (repository) via URL that does not include BIF identifier ses-02/ .... ... sub-A0001/ ... ... ``` where `A0001` is an Aachen-specific subject pseudocode, as described in the TRR379 SOP. When a new scan was completed: 1. A session subdataset is created, and deposited (see #10). 2. The subdataset is registered in the superdataset under subject pseudocode and session number (integer increment) 3. The DICOM superdataset is updated at its (consortium) public hosting location for members to become aware of the progress and to trigger potential CI runs. ### Data protection details Due to the nature of subdataset handling in DataLad, this superdataset will only contain the following information on a DICOM session subdataset: - URL of the location of the DataLad subdataset (not the location of the DICOMs!) - anonymous GITSHA identifier of the subdataset version - anonymous UUID identifier of the subdataset
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
git-annex
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
q02/phantom-mri-bids#12
No description provided.