Hi,
I was wondering if there is a way to prevent auto-selecting an option for Running a workflow? Quiet often users (especially novices) would re-run workflows without checking much the data that goes in thinking it will be the same as before. But because the options in drop down menus are auto-populated it seems the top option is always selected by default. For example, previously we had a single fasta file as reference and in the process of a workflow few other fasta files get generated. they appear above the previous fasta in the selection, so without paying attention people skip the input without really checking it.
Can we manually add a "blank" selection at the top to force users to select something?
Alex
On Wed, Oct 29, 2014 at 7:45 AM, Aleksey Jironkin < Aleksey.Jironkin@phe.gov.uk> wrote:
Hi,
I was wondering if there is a way to prevent auto-selecting an option for Running a workflow? Quiet often users (especially novices) would re-run workflows without checking much the data that goes in thinking it will be the same as before. But because the options in drop down menus are auto-populated it seems the top option is always selected by default. For example, previously we had a single fasta file as reference and in the process of a workflow few other fasta files get generated. they appear above the previous fasta in the selection, so without paying attention people skip the input without really checking it.
This behavior would be a bug - workflow parameters should be preserved. What release are you on - we fixed a bug related to this after the initial August release ( https://bitbucket.org/galaxy/galaxy-central/commits/5abd9fc76f7ad2eca013a1f8...) that should be available in the latest august stable tag.
Is it possible you were on the August release but don't have this fix?
If it is a bug and is still present in the latest stable branch if you could provide steps to reproduce it in a clean clone of Galaxy it could go a long way toward helping us track down a fix.
-John
Can we manually add a "blank" selection at the top to force users to select something?
Alex
-- Dr Aleksey Jironkin
Bioinformatician Bioinformatics Unit Infectious Disease Informatics Microbiologicy Services, Colindale Public Health England 61 Colindale Avenue London NW9 5EQ
Aleksey.Jironkin@phe.gov.uk
Tel: 020 83 276610
www.gov.uk/phe Follow us on Twitter @PHE_uk
Protecting and improving the nation’s health
Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Hi,
Thanks for your reply. I don;t think I have described well exactly what happened. The autoselect of the top option happens in all different parameters.
Because there is no "empty line" option in the select box, it "has" to select top element (whatever that may be). The elements get populated at run time so, if there has been new datasets generated with the same type, they will be populated above (seemingly) existing datasets. Thus making them autoselected when workflows run not necessarily the same workflow, but also different workflows altogether.
Current behaviour automatically pre-select a value in drop down box, and I was wondering if we can insert:
<option value="blank"></option>
Or something along those lines as a default for any dropdown, and the user not allowed to leave the dropdown box with "blank" value, which then forces the user to explicitely select something for that parameter.
Alex
On Wed, 2014-10-29 at 16:26 -0400, John Chilton wrote:
On Wed, Oct 29, 2014 at 7:45 AM, Aleksey Jironkin Aleksey.Jironkin@phe.gov.uk wrote:
Hi,
I was wondering if there is a way to prevent auto-selecting an
option
for Running a workflow? Quiet often users (especially novices) would re-run workflows without checking much the data that goes in
thinking it
will be the same as before. But because the options in drop down
menus
are auto-populated it seems the top option is always selected by default. For example, previously we had a single fasta file as
reference
and in the process of a workflow few other fasta files get
generated.
they appear above the previous fasta in the selection, so without
paying
attention people skip the input without really checking it.
This behavior would be a bug - workflow parameters should be preserved. What release are you on - we fixed a bug related to this after the initial August release (https://bitbucket.org/galaxy/galaxy-central/commits/5abd9fc76f7ad2eca013a1f8...) that should be available in the latest august stable tag.
Is it possible you were on the August release but don't have this fix?
If it is a bug and is still present in the latest stable branch if you could provide steps to reproduce it in a clean clone of Galaxy it could go a long way toward helping us track down a fix.
-John
Can we manually add a "blank" selection at the top to force users to select something?
Alex
-- Dr Aleksey Jironkin
Bioinformatician Bioinformatics Unit Infectious Disease Informatics Microbiologicy Services, Colindale Public Health England 61 Colindale Avenue London NW9 5EQ
Aleksey.Jironkin@phe.gov.uk
Tel: 020 83 276610
www.gov.uk/phe Follow us on Twitter @PHE_uk
Protecting and improving the nation’s health
Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Sorry for the delay - I think I understanding what you are saying now.
Are you connecting "inputs" to your datasets (they are at the botton of the workflow editor menu and many people miss them)? It is much more clear what the workflow runner has to do with these kind of inputs.
Short of that though - I think more people than not consider it a really nice feature that the inputs are prepopulated with items in the history that match that input. If you have just a couple datasets in in your history - it makes workflow running quicker and easier.
So unless there is an outcry from others that this is needed - I think the devteam is not going to add this. (Though by all means others should chime in and let me know if this would be a good feature and I am wrong.)
If you have some developer time to devote to this - I would be happy to walk you through where to look to modify this feature locally (with the caveat that Sam is going to make big changes to the workflow run page over the next few months so those diffs would like become conflicted quickly.)
-John
On Thu, Oct 30, 2014 at 4:47 AM, Aleksey Jironkin Aleksey.Jironkin@phe.gov.uk wrote:
Hi,
Thanks for your reply. I don;t think I have described well exactly what happened. The autoselect of the top option happens in all different parameters.
Because there is no "empty line" option in the select box, it "has" to select top element (whatever that may be). The elements get populated at run time so, if there has been new datasets generated with the same type, they will be populated above (seemingly) existing datasets. Thus making them autoselected when workflows run not necessarily the same workflow, but also different workflows altogether.
Current behaviour automatically pre-select a value in drop down box, and I was wondering if we can insert:
<option value="blank"></option>
Or something along those lines as a default for any dropdown, and the user not allowed to leave the dropdown box with "blank" value, which then forces the user to explicitely select something for that parameter.
Alex
On Wed, 2014-10-29 at 16:26 -0400, John Chilton wrote:
On Wed, Oct 29, 2014 at 7:45 AM, Aleksey Jironkin Aleksey.Jironkin@phe.gov.uk wrote:
Hi,
I was wondering if there is a way to prevent auto-selecting an
option
for Running a workflow? Quiet often users (especially novices) would re-run workflows without checking much the data that goes in
thinking it
will be the same as before. But because the options in drop down
menus
are auto-populated it seems the top option is always selected by default. For example, previously we had a single fasta file as
reference
and in the process of a workflow few other fasta files get
generated.
they appear above the previous fasta in the selection, so without
paying
attention people skip the input without really checking it.
This behavior would be a bug - workflow parameters should be preserved. What release are you on - we fixed a bug related to this after the initial August release (https://bitbucket.org/galaxy/galaxy-central/commits/5abd9fc76f7ad2eca013a1f8...) that should be available in the latest august stable tag.
Is it possible you were on the August release but don't have this fix?
If it is a bug and is still present in the latest stable branch if you could provide steps to reproduce it in a clean clone of Galaxy it could go a long way toward helping us track down a fix.
-John
Can we manually add a "blank" selection at the top to force users to select something?
Alex
-- Dr Aleksey Jironkin
Bioinformatician Bioinformatics Unit Infectious Disease Informatics Microbiologicy Services, Colindale Public Health England 61 Colindale Avenue London NW9 5EQ
Aleksey.Jironkin@phe.gov.uk
Tel: 020 83 276610
www.gov.uk/phe Follow us on Twitter @PHE_uk
Protecting and improving the nation’s health
Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
-- Dr Aleksey Jironkin
Bioinformatician Bioinformatics Unit Infectious Disease Informatics Microbiologicy Services, Colindale Public Health England 61 Colindale Avenue London NW9 5EQ
Aleksey.Jironkin@phe.gov.uk
Tel: 020 83 276610
www.gov.uk/phe Follow us on Twitter @PHE_uk
Protecting and improving the nation’s health
galaxy-dev@lists.galaxyproject.org
-
Aleksey Jironkin -
John Chilton