Back in February 2019 when the usegalaxy.* team were hacking together for a week we all converted our tool panels to use the same section names. Unfortunately, it turns out, the tool installation process doesn't exactly work that way.
It looks like tool_panel_section_label in an Ephemeris tool yaml becomes new_tool_panel_section_label in the API request. Through a series of levels ~~it turns out that instead of searching the toolbox by name/label, the label is converted to an ID with .lower().replace(' ', '_') and searches for that ID. If there's no match for that ID, a new section is created.
In #8 I expected that by passing the name of an existing section (ChIP-seq), it would be installed in to the existing section (which happens to have ID chip_seq). Instead, the install code searched for chip-seq and, not finding it, created a new section with the same name/label but with ID chip-seq.
This means that for usegalaxy.* common tools we need to:
- use identical section IDs, or
- fix Galaxy to find sections by name/label if an ID is not provided
IMO the best fix in the short term is to use identical section IDs, but that's maybe a little less flexible and requires looking in a shed_tool_conf.xml any time a new tool is added, rather than just looking at the tool panel in Galaxy.
ping @galaxyproject/universe-admins
Back in February 2019 when the usegalaxy.* team were hacking together for a week we all converted our tool panels to use the same section names. Unfortunately, it turns out, the tool installation process doesn't exactly work that way.
It looks like
tool_panel_section_labelin an Ephemeris tool yaml becomesnew_tool_panel_section_labelin the API request. Through a series of levels ~~it turns out that instead of searching the toolbox by name/label, the label is converted to an ID with.lower().replace(' ', '_')and searches for that ID. If there's no match for that ID, a new section is created.In #8 I expected that by passing the name of an existing section (
ChIP-seq), it would be installed in to the existing section (which happens to have IDchip_seq). Instead, the install code searched forchip-seqand, not finding it, created a new section with the same name/label but with IDchip-seq.This means that for usegalaxy.* common tools we need to:
IMO the best fix in the short term is to use identical section IDs, but that's maybe a little less flexible and requires looking in a shed_tool_conf.xml any time a new tool is added, rather than just looking at the tool panel in Galaxy.
ping @galaxyproject/universe-admins