Skip to content

ENH: Integration of Subject hierarchy into the Data module

The name of the subject hierarchy is not indicative to a user at all, and they may have difficulties finding out what the name actually covers. In the same time there is the Data module with an indicative name, but which has limited uses, and is mostly used to build transform hierarchies and for development purposes. It seems to make sense to "merge" the two modules, so that the now stable and fast subject hierarchy can be used where it is easiest to find.

  • Made the Data module widget tabbed, with Subject and Transform tabs. Subject contains the subject hierarchy, Transform contains the MRML tree from the current Data module (ModelHierarchy and AnnotationHierarchy were not migrated, as Model hierarchies are supported by subject hierarchy, and if display properties are to be set, then the Models module is needed anyway, and Annotations is considered deprecated - it is also supported by SH by default too)
  • Subject hierarchy made a hidden module, and all content removed from its module widget (so that it does not need to be maintained in two places
  • Data module icon replaced with the subject hierarchy icon, and Subject hierarchy replaced by Data in the favorite module toolbar
  • Added a button to "Explore Loaded Data" in Welcome module, and also updated text

Merge request reports

Loading