Documentation/Labs/DICOMExport - Revision history

Pinter: /* Design and implementation */

2014-12-08T18:03:13Z

Design and implementation

Pinter: /* Code branch on github */

2014-11-11T20:58:38Z

Code branch on github

Pinter: /* Future features */

2014-11-11T20:53:38Z

Future features

Pinter: Move Notes section to bottom (so that actionable items are in one bunch: future features, issues, discusisons)

2014-11-07T15:25:45Z

Move Notes section to bottom (so that actionable items are in one bunch: future features, issues, discusisons)

Pinter: /* Future features */

2014-11-07T15:24:09Z

Future features

Pinter: /* Issues */

2014-11-06T21:27:34Z

Issues

Pinter: /* Issues */

2014-11-06T21:26:59Z

Issues

Pinter: /* Notes */

2014-11-05T22:37:17Z

Notes

Pinter: /* Future features */

2014-11-05T19:03:34Z

Future features

Pinter: /* Issues */

2014-11-05T18:56:28Z

Issues

@@ Line 16: / Line 16: @@
 * 2. Select export type: Once the user selected a node, the DICOM plugins generate exportables for the series they can export. The list of the results appear in this section, grouped by plugin. The confidence number will be the average of the confidence numbers for the individual series for that plugin.
 * 3. Edit DICOM tags:
-** Pseudo-tags: the "tags" are not real DICOM tags with (XXXX,YYYY) identifiers, they are just concepts ("pseudo-tags"), that the DICOM plugins prompt to the user to fill out. It has been decided to go this way, as it would be extremely hard to program the whole DICOM tag structure into Slicer. Also it would not be particularly useful, as most tags will be auto-populated by the DICOM plugin, and just some need to be edited by the user.
+** Pseudo-tags: the "tags" are not real DICOM tags with (XXXX,YYYY) identifiers, they are just concepts ("pseudo-tags"), that the DICOM plugins prompt to the user to fill out. It has been decided to go this way, as (1) It would be extremely hard to program the whole DICOM tag structure into Slicer, (2) It would not be particularly useful, as most tags will be auto-populated by the DICOM plugin, and just some need to be edited by the user, and (3) The plugins can expose other export options in this list (e.g. compession, naming convention)
 ** The DICOM tag editor consists of a list of tables. Tables for the common tags for the patient and study on the top, and the tags for the individual series below them (see image about tag editor below).
 * Save tags on export: Checkbox to allow saving the tags back to the MRML nodes as attributes. Off by default because it is expected that in most cases these values are temporary for the export session.

@@ Line 32: / Line 32: @@
 = Code branch on github =
-https://github.com/cpinter/Slicer/tree/srt55-dicom-export
+* https://github.com/cpinter/Slicer/tree/srt55-dicom-export
+** Compare to master: https://github.com/cpinter/Slicer/compare/Slicer:master...cpinter:srt55-dicom-export
-(SlicerRT branch: https://subversion.assembla.com/svn/slicerrt/branches/DICOMExport )
+* (SlicerRT branch: https://subversion.assembla.com/svn/slicerrt/branches/DICOMExport )
 = Slicer core changes =

@@ Line 54: / Line 54: @@
 * Show only nodes that have at least one exportable (plugin that can export them)
 * Multi-select series in tree or add checkboxes to select what to export in a more granular way
 = Issues =

@@ Line 59: / Line 59: @@
 * Save on tags doesn't change the patient and study node names. It would be quite hard to synchronize. If the need arises, it can be implemented.
 * Scalar volume export creates a different StudyInstanceUID even if study ID and description are the same. Thus two studies with the exact same information appear under a patient if two volumes are exported.
 = Topics to discuss =
@@ Line 77: / Line 69: @@
 ** Separate button for Export to database and Export to local folder?
 ** Should we import the exported data into the DICOM DB even if the output folder is not a database directory (currently it's always imported)

@@ Line 52: / Line 52: @@
 * Anonymize button to wipe out patient info
 * Append to existing study. Currently only exporting to new studies are possible.
 * Multi-select series in tree or add checkboxes to select what to export in a more granular way

← Older revision		Revision as of 22:37, 5 November 2014
Line 66:		Line 66:
	\|[[Image:DICOM_Export_Dialog_4.3.1.png\|thumb\|right\|417px\|DICOM Export dialog in Slicer 4.3.1]]		\|[[Image:DICOM_Export_Dialog_4.3.1.png\|thumb\|right\|417px\|DICOM Export dialog in Slicer 4.3.1]]
	\|}		\|}
		+
		+	= Topics to discuss =
		+	Need consensus in these, as there are different opinions.
		+	* Export to entire scene
		+	** Needed at all? ("Saving the mrb inside a secondary capture is a hack, not really a DICOM export.")
		+	** If yes, should we move it to another place?
		+	* Output folder
		+	** Always export to temporary location first to avoid overwrite?
		+	** Separate button for Export to database and Export to local folder?
		+	** Should we import the exported data into the DICOM DB even if the output folder is not a database directory (currently it's always imported)

@@ Line 56: / Line 56: @@
 * Bug reports and feature requests are welcome!
 * Save on tags doesn't change the patient and study node names. It would be quite hard to synchronize. If the need arises, it can be implemented.
 = Notes =