Difference between revisions of "2014 Summer Project Week:Subject hierarchy integration"
From NAMIC Wiki
| Line 23: | Line 23: | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
| − | * Collect feedback | + | * Collect feedback; Please come and find me (Csaba) if you have |
| + | ** used it and have any comments | ||
| + | ** a special data type which needs a role plugin to be implemented | ||
| + | ** a feature that would need to have a simplified workflow and can be supported by a function plugin | ||
* Go through the non-trivial items on the list with the core group and make decisions | * Go through the non-trivial items on the list with the core group and make decisions | ||
* Implement fixes and changes, do testing | * Implement fixes and changes, do testing | ||
Revision as of 17:43, 23 June 2014
Home < 2014 Summer Project Week:Subject hierarchy integration
Module UI
Key Investigators
- Csaba Pinter, Queen's
- Jean-Christophe Fillion-Robin, Kitware
- Steve Pieper, Isomics
- Andras Lasso, Queen's
Project Description
The new Subject hierarchy module and mechanism has been integrated into Slicer core recently, but has some issues and requests that need to be fixed.
Resources:
Objective
- Finalize the Subject hierarchy module and mechanism, fix outstanding issues and bugs
Approach, Plan
- Collect feedback; Please come and find me (Csaba) if you have
- used it and have any comments
- a special data type which needs a role plugin to be implemented
- a feature that would need to have a simplified workflow and can be supported by a function plugin
- Go through the non-trivial items on the list with the core group and make decisions
- Implement fixes and changes, do testing
