This section contains one setting, scan type mapping, that did not fit elsewhere, and also contains links that will be useful when managing your site.
Scan Type Mapping and Development Utilities
Scan Type Mapping
When sessions are imported into XNAT, their scan types are defined in the original DICOM files. This can be useful, but it may also contain tiny variations that are no longer relevant to your project. Scan Type Mapping allows you to define rules for how XNAT should rename scan types after they have been uploaded. These can be defined for a given project by clicking on the Scan Type Cleanup option in the Actions box for a project. By default, Scan Type Mapping is enabled, but if you do not want anyone to be able to use this feature on your site, you can disable it by clicking the switch box or the word Enabled. It can be re-enabled by clicking the switch box again or clicking on the word Disabled.
XNAT Spawner elements control what shows up in the admin UI. If you have customized XNAT and want there to be new administrator options for your customizations, you can add new options by clicking 'Manage Spawner Elements'. Spawner elements are configured using YAML, so some knowledge of YAML is required.
Swagger enables you to directly access the XNAT REST API through the UI. If you click the View the Swagger Page, click on the section of the REST API you want to access, and then click on the REST call you want to make, you can then enter any parameters you want and click 'Try it out!' to issue the REST call. While some older XNAT REST calls are not yet configured to show up in Swagger, all new ones should be. Swagger is a great way to easily issue REST calls without worrying about making sure you have the right command line syntax.