All issues

Search results

Add best practice to add version to data table for new data managers

Status: Open.

#79 In galaxy-iuc/standards;

· paulzierep opened on Sep 30, 2024

Introduce creator tag in xml_order in top level tool.xml file

Status: Open.

#75 In galaxy-iuc/standards;

· hechth opened on Jul 24, 2023

Tabs should be permitted, maybe even mandatory.

Status: Open.

#73 In galaxy-iuc/standards;

· hexylena opened on Nov 14, 2022

Clarify how license tags should be used for tools

Status: Open.

#72 In galaxy-iuc/standards;

· elichad opened on Oct 10, 2022

Guidelines for additional output parameters

Status: Open.

#66 In galaxy-iuc/standards;

· bernt-matthias opened on Oct 5, 2021

Specifying a tool maintainer in .shed.yml files

Status: Open.

#65 In galaxy-iuc/standards;

· simonbray opened on Jul 20, 2021

Documentation of the commands to run to test a tool

Status: Open.

#64 In galaxy-iuc/standards;

· bebatut opened on Apr 14, 2021

Recommend not redirecting stderr

Status: Open.

#57 In galaxy-iuc/standards;

· mvdbeek opened on Dec 19, 2019

Recommendations on arbitrary parameter fields (security risks?)

discussion

Status: Open.

#56 In galaxy-iuc/standards;

· peterjc opened on Aug 26, 2019

Change "Tool on data N" output file naming to something without spaces?

Status: Open.

#53 In galaxy-iuc/standards;

· mblue9 opened on Apr 21, 2018

When should we write separate scripts and when should we use configfiles

Status: Open.

#49 In galaxy-iuc/standards;

· mvdbeek opened on Nov 9, 2017

EDAM ontology topics should be applied to tools

Status: Open.

#45 In galaxy-iuc/standards;

· hexylena opened on Jun 28, 2017