Logic to only add open link to tools that are available on the lab server

[paulzierep]

Despite our best efforts, there will be servers that will not install all tools for all communities. We cannot fix that on our side.
So once the tool table is available in the labs, there should be a logic to handle that.
Some ideas from my side:

• Show all tools from a community, but only add links to tools that are available on this server
• Add a way to filter to only show the tools on that server

[paulzierep]

I assume we would need to create one tools section for each server. And then only put links that work on that server. Is there a way to use a different section depending on the server ? @neoformit ?

[neoformit]

A way to filter only the tools on that server

I think this is the right thing to do, showing tools that aren't installed would be annoying as a user.

I think you're looking for the (currently undocumented) exclude_from key:

galaxy_codex/communities/spoc/lab/sections/1_beginner.yml

Lines 212 to 218 in dda9c0d

	- title_md: How can I increase my storage quota?
	description_md: >
	Please submit a quota request if your Galaxy account reaches its data storage limit. Requests are usually provisioned quickly if you provide a reasonable use case for your request.
	button_md: Request
	button_link: "{{ quota_request_url }}"
	exclude_from:
	- usegalaxy.org

This can be used to exclude specific blocks of the Sections data from particular hostname(s).

[nomadscientist]

1. Why are you putting the whole Catalog tool table on labs? That's excessive when there's also a Tool Panel.

2. I absolutely think that any tools missing that are explicitly linked in the curated Lab and/or Galaxy Training section should send some sort of alert to the admin upon spinning up a lab to tell them to install that tool. This is a fantastic idea.

3. I think that the CoDex/Labs section should contain generalised, not server-specific, tool panel. Then individual servers, if they choose not to install all those tools, can overwrite it with their own set-up however they choose. But that shouldn't be in the CoDex.

4. Exclude from is a GREAT shout.

[neoformit]

2. Sounds like a good idea, though not easy to implement because the Labs Engine doesn't have a contact email for each lab. Two solutions came to mind and this is the one I liked most:

• An additional URL parameter &test_tools=true that can be added to a Lab URL and would display the results in the browser in real-time. You could just send that URL to the Galaxy admin to share the report with them.