folder import command should be used if you are importing data that you previously downloaded from Flywheel, or if you are importing data that was shared from another Flywheel site.
folder import command requires your directory of data to exactly match the the Flywheel hierarchy. Below is the basic Flywheel hierarchy:
Follow these instructions to download and install the Flywheel CLI. If you cannot download the Flywheel CLI to your computer, you can upload smaller batches of files using your web browser.
Unsupported upload method for site, group, or project de-id profiles
Use one of these supported methods if you use site, group, or project de-id profiles.
Follow these steps to import your structured directory to Flywheel:
If the directory you are importing does not exactly match the directory shown in the image above, consider using another method to import your images. For example, if all of your images are DICOMS, consider using our dicom importer to automatically determine containers in Flywheel for your data. This option also groups images by subjects and sessions. Learn about the other ways to import data.
Open Terminal or Windows Command Prompt.
Note the location of the parent folder for your data.
Enter the import folder command:
fw import folder <Folder you are importing> <optional flags>
fw import folder ~/Desktop/MultiCenterStudy --group psychology --dicom dicomsubfolder1
--groupflag designates a group in Flywheel where the data should be imported. This overwrites whatever the name of the folder is in the directory you are uploading. The
--dicomflag takes subfolders with DICOM images, analyzes them, zips them, and adds them as acquisitions. Learn more about the optional flags for the import folder command.
Review the hierarchy and scan summary to make sure it matches what you expect.
Enter yes to begin importing.
The Flywheel CLI displays its import progress
Sign in to Flywheel to view your data.
Each level in the Flywheel hierarchy must be specified during import. This means you must either:
Have a folder for each container (Group, Project, Subject, Session, Acquisitions, and images) OR
Manually configure the container using an optional flag. For example:
--project <project label>. For more information about the optional flags, see our reference guide.