View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003474Slicer4Core: Documentation and Wikipublic2013-11-04 10:542018-03-02 11:06
Reporterfinetjul Assigned Tojcfr  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version 
Target VersionSlicer 4.5.0-1Fixed in VersionSlicer 4.5.0-1 
Summary0003474: Consolidate list of modules.
Description

It is not clear to know if a module is built-in Slicer or installable as an extension. The provenance of the module should be clearly reported on the wiki.

TagsNo tags attached.

Relationships

related to 0001602 acknowledgedjcfr "tag" to identify CLI executables 
related to 0002033 closedmatthew-woehlke Mechanism to list extensions on top of Documentation page 
related to 0001543 closedmhalle Install CategoryTree extension 
related to 0002843 closedjcfr consolidate the list of extensions which are visible in the extension manager and the list which is visible on the slicer wiki 

Activities

jcfr

jcfr

2014-05-12 19:16

administrator   ~0011734

Two possible approaches:

1) Installing the following mediawiki extensions and update the page to list both the module and extension category + within a given page, we would also detect if a module belong to the extension category by using "PageInCat"

  • CategoryTree (See 0001543)

  • PageInCat (See [1]) - Require media wiki upgrade

    2) Writing a python script that would extend the existing Metadata page [2] and mention if a module belong or not to an extension ...

[1] https://www.mediawiki.org/wiki/Extension:PageInCat
[2] http://wiki.slicer.org/slicerWiki/index.php/Documentation/Nightly/ModulesMetadata
halazar

halazar

2014-05-14 11:15

reporter   ~0011847

I attempted to add the latest CategoryTree release to the slicer.org wiki.

However, when I enabled it in LocalSettings.php, the wiki broke in such a way that it returns empty pages.

I'll have to investigate more....
jcfr

jcfr

2015-11-02 05:01

administrator   ~0013475

Provenance of modules is now indicated either using "Built-in" or the a link to the associated extension.

Issue History

Date Modified Username Field Change
2013-11-04 10:54 jcfr New Issue
2013-11-04 10:54 jcfr Status new => assigned
2013-11-04 10:54 jcfr Assigned To => jcfr
2013-11-04 10:54 jcfr Reporter jcfr => finetjul
2013-11-04 10:54 jcfr Target Version => Slicer 4.3.2
2014-03-06 10:15 nicole Target Version Slicer 4.3.2 => Slicer 4.4.0
2014-05-12 18:59 jcfr Relationship added related to 0001602
2014-05-12 19:05 jcfr Relationship added related to 0002033
2014-05-12 19:05 jcfr Relationship added related to 0001543
2014-05-12 19:16 jcfr Note Added: 0011734
2014-05-14 11:15 halazar Note Added: 0011847
2014-07-30 19:09 jcfr Relationship added related to 0002843
2014-11-02 03:31 jcfr Target Version Slicer 4.4.0 => Slicer 4.4.1
2015-09-01 10:29 jcfr Target Version Slicer 4.4.1 => Slicer 4.5.0-1
2015-11-02 05:01 jcfr Note Added: 0013475
2015-11-02 05:01 jcfr Status assigned => resolved
2015-11-02 05:01 jcfr Fixed in Version => Slicer 4.5.0-1
2015-11-02 05:01 jcfr Resolution open => fixed
2016-06-20 14:15 jcfr Category Core: Documentation & Wiki => Core: Documentation and Wiki
2018-03-02 11:06 jcfr Status resolved => closed