Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Require an "active" database/genome index selection on tool forms #4499

Open
jennaj opened this issue Aug 25, 2017 · 1 comment
Open

Require an "active" database/genome index selection on tool forms #4499

jennaj opened this issue Aug 25, 2017 · 1 comment

Comments

@jennaj
Copy link
Member

jennaj commented Aug 25, 2017

Many tools have the genome select list propagated where the first in the list is automatically selected by default.

It would avoid a common usage error (user doesn't change the genome) to have the first "entry" in the list state "Select database" or something else similar. Then trap the required missing database selection at job submission (model after existing required field warnings).

Even if we just modified mapping tools, the majority of reported usage issues due to genome form-entry mistakes would be avoided. Examples: BWA/BWA-MEM, Bowtie2, HISAT2

Update: recent examples

@jennaj
Copy link
Member Author

jennaj commented Mar 3, 2018

Same usage issue, different tool: galaxyproject/tools-iuc#1754

Update: Featurecounts modified to require active selection or tool form will not submit. Great! Testing at usegalaxy.org with updated tool v 1.6.0.3 galaxyproject/usegalaxy-playbook#52

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants