Note: data could also come from web browser GUI or through DICOM transfer. Response: Script looks for return value, parses XCEDE for the ID of each uploaded image, or parses error XML and posts message if upload failed. Upload file plus XML file that associates the file, project and visit. An investigator uploads all tagged data from a study (using an upload script, or a webGUI or something outside of Slicer) and associates it with the new project – for instance: Probably done through web browser interface, but we should allow programmatic control at some point. (not sure how to do this on command line - should discuss this.) An investigator creates a new project in the hosted repository: system-generated ID is returned to user, who can accept or reject that ID.Īssuming also that PUT and POST are swapped on the spreadsheet Jeff sent last week.no placeholder ID is supplied and the system just generates a unique ID.user may supply a preferred placeholder ID to which the back end applies a uniqueness check.There are different ways in which an ID might be generated for an element. Each element can also have a user-assigned label without a uniquenss requirement (like scan001), which may be a more comfortable way for the user to refer to it.CompositeIDs are made globally unique by appending the uri of the hosted repository.Each element's ID is made unique by the back end, so that each visit, acquisition, subject, study, etc.Each visit (such as OAS1_0006_MR1) may contain multiple acquisitions, assessments, and derived data.Step6: When finished, a researcher uploads completed work or work in progress and tags the work appropriately.įor example, we’ll use the public OASIS brains dataset on XNAT, and let “composite ID” for a visit be OAS1_0006_MR1, or OAS1_0009_MR1, etc.Step5: A researcher downloads some subset of those assignments in an XCEDE catalog, opens the catalog with Slicer and creates a label map.Step4: A researcher queries for all acquisition segmentations assigned to them.Step3: The investigator then assigns each acquisition to a researcher for a segmentation task.Step2: Later, the investigator queries for all “Acquisitions” uploaded as part of the study. Step1: Investigator uploads data from a study and associates it with the project.Step0: Investigator creates a new project on the hosted repository.Slicer use-case #1: Managing image processing project in a Neuroscience Lab Overview workflow use case where investigator assigns processing tasks to RAs using tags to keep track of processing state.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |