Result class of a File upload operation as returned by the VSD
Class representing an authenticated session with the VSD.
Class representing an authenticated session with the VSD. Once successfully created, all operations on the VSD can be performed by accessing methods of this class
Common VSD Object information that is present for all supported object types The sub-fields names should be self-explanatory.
Common VSD Object information that is present for all supported object types The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Class of Folders on the VSD The sub-fields names should be self-explanatory.
Class of Folders on the VSD The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Class of groups (user groups) on the VSD The sub-fields names should be self-explanatory.
Class of groups (user groups) on the VSD The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Class of Links on the VSD.
Class of Links on the VSD. a link indicates a relation between 2 objects eg. object 2 is the segmentation of the raw object 1 The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Class of Image modalities supported by the VSD (CT, OT,).
Class of Image modalities supported by the VSD (CT, OT,). A detailed list of modality names (not necessarily all supported by the VSD) can be found here The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Class indicating rights attributed to a group on a VSD object The sub-fields names should be self-explanatory.
Class indicating rights attributed to a group on a VSD object The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Relation between an ontology item and a VSD object.
Relation between an ontology item and a VSD object. This is used to say that the VSD object is a depiction of a particular organ The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Class of rights than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory.
Class of rights than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Class identifying an object type on the VSD The sub-fields names should be self-explanatory.
Class identifying an object type on the VSD The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Class indicating rights attributed to a users on a VSD object The sub-fields names should be self-explanatory.
Class indicating rights attributed to a users on a VSD object The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Class of lists of VSDOntology returned upon request
Class of VSD Ontologies.
Class of VSD Ontologies. An ontology on the VSD, is a set of statndardized denomination of anatomical organs. An example of such an ontology is the Foundational Model of Anatomy (FMA) The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Class of an item belonging to an ontology supported by the VSD.
Class of an item belonging to an ontology supported by the VSD. This is typically the denomination of a particular organ of interest in the given ontology. The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Internal class to handle paginated responses.
Internal class to handle paginated responses.
(required to be public due to Marshalling implicits)
Internal class to handle paginated responses.
Internal class to handle paginated responses.
(required to be public due to Marshalling implicits)
Information about RawImage such as slice thickness, inter-spacing, signal strength, modality, ..
Information about RawImage such as slice thickness, inter-spacing, signal strength, modality, .. The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Information for VSD Objects of type RawImage (i.e.
Information for VSD Objects of type RawImage (i.e. raw intensity images). Additionally to the common object information, this adds optional fields such as slice thickness, inter-spacing, signal strength, modality, .. The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Information about SegmentationImage such as segmentation method, and a description ..
Information about SegmentationImage such as segmentation method, and a description .. The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Class of Segmentation methods supported by the VSD.
Class of Segmentation methods supported by the VSD. These are for example: Manual, Automatic. Semi-Automatic The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Information for VSD Objects of type Segmentation (i.e.
Information for VSD Objects of type Segmentation (i.e. binary images). Additionally to the common object information, this adds optional fields such as segmentation method, and a description .. The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Information for VSD Objects of type Statistical Model (i.e.
Information for VSD Objects of type Statistical Model (i.e. h5 files) The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
VSDURL is the first clsss pointer to objects on the VSD.
VSDURL is the first clsss pointer to objects on the VSD. It can point to Files, Objects, Folders, Links, Ontologies, etc ... Most of the client's API requests rely on a VSDURL to identify the objects to manipulate.
actual URL of the resource
Class identifying a user on the VSD The sub-fields names should be self-explanatory.
Class identifying a user on the VSD The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Factory for VSDClient class
ClinicalStudyData object type The sub-fields names should be self-explanatory.
ClinicalStudyData object type The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
ClinicalStudyDefinition object type The sub-fields names should be self-explanatory.
ClinicalStudyDefinition object type The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
* Download right than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory.
* Download right than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Edit right than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory.
Edit right than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
GenomicPlatform object type The sub-fields names should be self-explanatory.
GenomicPlatform object type The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
GenomicSample object type The sub-fields names should be self-explanatory.
GenomicSample object type The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
GenomicSeries object type The sub-fields names should be self-explanatory.
GenomicSeries object type The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Defines variables required de/serializing VSD related classes from/to Json
Manage right than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory.
Manage right than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
None right than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory.
None right than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Owner right than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory.
Owner right than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Plain object type The sub-fields names should be self-explanatory.
Plain object type The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
PlainSubject object type The sub-fields names should be self-explanatory.
PlainSubject object type The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
RawImage object type The sub-fields names should be self-explanatory.
RawImage object type The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Read right than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory.
Read right than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
SegmentationImage object type The sub-fields names should be self-explanatory.
SegmentationImage object type The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
StatisticalModel object type The sub-fields names should be self-explanatory.
StatisticalModel object type The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Study object type The sub-fields names should be self-explanatory.
Study object type The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Subject object type The sub-fields names should be self-explanatory.
Subject object type The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
SurfaceModel object type The sub-fields names should be self-explanatory.
SurfaceModel object type The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Visit right than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory.
Visit right than can be attributed to VSD objects and Folders The sub-fields names should be self-explanatory. In case of doubt, please check the VSD's API doc
Result class of a File upload operation as returned by the VSD
url of the successfully uploaded file
url of the created object associated to this file. For example,several upload Dicom files will have the same related VSD object