# Case Iterator with segment editor

**URL:** <https://discourse.slicer.org/t/case-iterator-with-segment-editor/8340>\
**Category:** Support\
**Created:** [September 9, 2019, 5:05am UTC](https://discourse.slicer.org/t/case-iterator-with-segment-editor/8340 "2019-09-09T05:05:07Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [September 12, 2019, 12:57pm UTC](https://discourse.slicer.org/t/case-iterator-with-segment-editor/8340/7 "2019-09-12T12:57:52Z")

</div>

Typing a segment name each time seems quite error-prone (typos, differences in spelling, etc. can all cause issues). It would be useful to initialize each new segmentation node by copying empty segments with pre-populated names (and terminology) from a “template” segmentation node.

Recent Slicer Preview Releases facilitate this workflow by adding “completion state” (new, being edited, completed, flagged) to each segment - see details here: [New feature: Search and filter in segments table](https://discourse.slicer.org/t/new-feature-search-and-filter-in-segments-table/7827).

---

_[View the full topic](https://discourse.slicer.org/t/case-iterator-with-segment-editor/8340)._