View Issue Details

IDProjectCategoryView StatusLast Update
0002254Slicer4Module DICOMpublic2018-05-30 00:14
ReporterfedorovAssigned Topieper 
PrioritynormalSeveritymajorReproducibilityalways
Status acknowledgedResolutionopen 
Product VersionSlicer 4.1.1 
Target VersionbacklogFixed in Version 
Summary0002254: Unable to create Slicer DICOM data bundle
Description

I have the error in the popup window as attached.

The scene contains a 3-slice image loaded from DICOM database, and a segmentation label with a contour on one slice.

TagsNo tags attached.

Relationships

related to 0002313 assignedpieper Implement onSDBSaveToDCMActionTriggered 

Activities

2012-06-25 07:25

 

jcfr

jcfr

2014-05-13 09:40

administrator   ~0011765

@Steve: If this is something you plan on addressing before the release, please re-target. Thanks

lassoan

lassoan

2017-06-10 00:41

developer   ~0014718

Creating Slicer DICOM data bundles is still quite complicated process.
Feature is now available from Data module: right-click, Export to DICOM, Export entire scene.
However, there is no way to choose an output directory, temporary files remain in the same directory as the generated SlicerDataBundle.dcm, it's not clear how to specify patient information, when the .dcm file is imported it is difficult to find that under which patient it shows up.

lassoan

lassoan

2017-06-10 00:42

developer   ~0014719

The feature is certainly difficult to use, but it is somewhat usable and this issue has been open for years, so it is definitely not a blocking issue.

fedorov

fedorov

2017-06-10 13:58

developer   ~0014735

My workaround for this one - forget about the existence of this feature ;-) Same applies to using Slicer MRML scene file.

lassoan

lassoan

2017-06-10 15:23

developer   ~0014737

This is certainly a niche feature, so it is perfectly fine not to use it. It is a quite limited alternative to proper DICOM export. We should probably not invest any time into improving it but spend the time with making proper DICOM export better. Which means that we just have to decide when to remove this. I'll ask for user feedback in the forum.

lassoan

lassoan

2017-06-10 15:47

developer   ~0014738

Last edited: 2017-06-10 15:48

View 2 revisions

Added a poll in the Slicer forum to know how many people know about it/use it:
https://discourse.slicer.org/t/who-uses-dicom-data-bundle/475

lassoan

lassoan

2018-05-30 00:14

developer   ~0015801

Retarget stale issues to backlog.

Issue History

Date Modified Username Field Change
2012-06-25 07:25 fedorov New Issue
2012-06-25 07:25 fedorov Status new => assigned
2012-06-25 07:25 fedorov Assigned To => pieper
2012-06-25 07:25 fedorov File Added: Screen shot 2012-06-25 at 11.23.31 .png
2012-08-22 05:56 jcfr Target Version => Slicer 4.3.0
2013-07-05 07:37 pieper Target Version Slicer 4.3.0 => Slicer 4.4.0
2014-03-06 13:28 pieper Relationship added related to 0002313
2014-03-07 05:43 pieper Status assigned => acknowledged
2014-05-13 09:40 jcfr Target Version Slicer 4.4.0 =>
2014-05-13 09:40 jcfr Note Added: 0011765
2017-06-10 00:41 lassoan Note Added: 0014718
2017-06-10 00:42 lassoan Severity block => major
2017-06-10 00:42 lassoan Note Added: 0014719
2017-06-10 13:58 fedorov Note Added: 0014735
2017-06-10 15:23 lassoan Note Added: 0014737
2017-06-10 15:47 lassoan Note Added: 0014738
2017-06-10 15:48 lassoan Note Edited: 0014738 View Revisions
2018-05-30 00:14 lassoan Target Version => backlog
2018-05-30 00:14 lassoan Note Added: 0015801