Extension Catalogue search improvements

[muratmaga]

During the discussions of a new extension, it become clear that extension catalogue naming conventions are too restrictive. For example, an extension name cannot have spaces, since the label name is also used for project name.

Search in the extension catalogue also doesn’t search for the project descriptions. More detailed discussion can be found here: ENH: add SlicerDeCA extension by smrolfe · Pull Request #2146 · Slicer/ExtensionsIndex · GitHub

I also think that if we do NOT want extensions to have Slicer in their extension name, we should stop requiring repos to have Slicer prefix. It perhaps makes sense for existing tools (e.g., ANTs, MONAI) that are ported to Slicer (so it becomes SlicerANTs, SlicerMONAI), but otherwise it is awkward for the project name and the repo not to be the same for extension specifically developer for Slicer.

This is meant to start a discussion of what I perceive shortcomings of the current extension naming requirements.

[jamesobutler (James Butler)]

@muratmaga

but otherwise it is awkward for the project name and the repo not to be the same

It currently serves different search functionality as the CMakeLists.txt project name is the extension name that users will be searching with within Slicer. The GitHub repository name is for searchability within GitHub to find Slicer associated repositories. That is in addition to the 3d-slicer-extension GitHub topic which is to be used as mentioned in the checklist for submitting a new Slicer extension.

Luckily the Slicer Extension Wizard can set up all these naming schemes appropriately. If it is not currently doing this, we could update that code to fix any issues.