DICOM import can be attempted before creating database

Actually on this note I should mention that behavior of DICOMBrowser for the new users of Slicer is confusing. See the screenshot below. Even though there is an error message indicating that the DICOM DB needs to be created/specified, you can still click the import tab, and actually go through the import process (but end of with 0 patients imported).

Either make the error message much more visible, or gray out the import tab until a database is created. I am not sure if this is @Patrick issue, but during the workshop this threw off a lot of new users…

@lassoan @pieper


Thanks for reporting this @muratmaga. As far as I know this is new behavior with the redesign of the module. @lassoan was there a reason not to auto-create a database in the user’s Documents folder?

There were lots of issues in the old DICOM browser with actions automatically happening (and failing) and showing error popups, blocking the user (or automatic scripts) or covering other popups. The main design now is that we never block the GUI, show high-level errors/warnings on the GUI and let the users dig into the logs if they want to know more about the exact underlying issues.

I agree that we should give earlier feedback to the user that DICOM database has not been created yet. Maybe we could even try to automatically create one when needed. We must be very careful to do these at the user interface level to make sure we never block any test or batch processing scripts by GUI popups.

1 Like

Yes, why don’t we just disable the import button if there’s no valid database?