These keys can be substituted for the full XML Path when referencing variables in PUT or POST procedures. When using the querystring to define your variables, you should include the ?req_format parameter with a value of "qs" to prevent the body of the message from being parsed.
Panel
Contents
Table of Contents
xsiType
All PUT and POST operations allow you to use the querystring parameter 'xsiType' to specify the related data type in your schema. This is only necessary when the level you are referencing could have multiple extensions. For example, /data/projects/{ID}/subjects/{ID}/experiments/{ID}. This could be an instance of an xnat:mrSessionData, xnat:petSessionData, or any other data type which extends xnat:subjectAssessorData. So, if you are not including XML to describe your resource, you must use the xsiType parameter (before any other parameters) to specify which type of item you are creating. For example:
These keys can be substituted for the full XML Path when referencing variables in PUT or POST procedures. When using the querystring to define your variables, you should include the
?req_formatparameter with a value of "qs" to prevent the body of the message from being parsed.Contents
xsiType
All PUT and POST operations allow you to use the querystring parameter '
xsiType' to specify the related data type in your schema. This is only necessary when the level you are referencing could have multiple extensions. For example,/data/projects/{ID}/subjects/{ID}/experiments/{ID}. This could be an instance of an xnat:mrSessionData, xnat:petSessionData, or any other data type which extends xnat:subjectAssessorData. So, if you are not including XML to describe your resource, you must use the xsiType parameter (before any other parameters) to specify which type of item you are creating. For example:/data/projects/{ID}/subjects/{ID}/experiments/{ID}?xsiType=xnat:mrSessionData