-
Notifications
You must be signed in to change notification settings - Fork 183
Open
Labels
Area: APIPR or issue related to the APIPR or issue related to the APIArea: UIPR or issue related to the user interfacePR or issue related to the user interfaceCategory: FeaturePR or issue that aims to introduce a new featurePR or issue that aims to introduce a new featureCategory: SecurityPR or issue that aims to improve securityPR or issue that aims to improve securityLanguage: SQLPR or issue that update SQL codePR or issue that update SQL codeModule: dicom_archivePR or issue related to dicom_archive modulePR or issue related to dicom_archive module
Description
While creating the Open PREVENT-AD instance of LORIS, it was important to disable the disable of DICOM files out of concern for privacy and to fulfill the study's ethical commitments.
This was done in an ad-hoc way and it would probably benefit future studies going open to have a configuration option that would optionally disable DICOM downloads.
The PR linked below indicates all the places in LORIS where this can be done.
https://github.com/johnsaigle/Loris/pull/16
TODO:
- Create a config setting in the 0000-00-00 table
enableDICOMDownload
with a default of true.- Also a corresponding patch in SQL/New_patches
- For each place in LORIS where downloading DICOMs is possible, check if the above setting is false
- If so, disable/hide all UI elements allowing download
- The file
htdocs/mri/jiv/get_file.php
should check this config setting and return a403
response when DICOM files are requested. This must be done in case a user tries to access the files directly even when UI elements allowing this are not shown in LORIS. - DICOM download must also be disabled via the API. I'm not sure where this takes place but it should also give a
403
if the setting is disabled. - Update Raisinbread files
Metadata
Metadata
Assignees
Labels
Area: APIPR or issue related to the APIPR or issue related to the APIArea: UIPR or issue related to the user interfacePR or issue related to the user interfaceCategory: FeaturePR or issue that aims to introduce a new featurePR or issue that aims to introduce a new featureCategory: SecurityPR or issue that aims to improve securityPR or issue that aims to improve securityLanguage: SQLPR or issue that update SQL codePR or issue that update SQL codeModule: dicom_archivePR or issue related to dicom_archive modulePR or issue related to dicom_archive module