Another idea for the https://galaxyproject.github.io/training-material/ site itself -- any thoughts on building a search function into it? I end of using google a lot to find which tutorials have certain tools, datatypes, and other various operations. Going back to use the search function in https://galaxyproject.org/search/ isn't obvious for users, and can produce a lot of noisy results.
I can make that into a ticket. just didn't want to rehash something that is already planned for
or discarded as a terrible idea :)
I guess updating the tutorial with a tip, to make sure the fastq tpye does match is a good way
it uses TeSS to search the site for terms, it probably won't find tools currently.
We can look at exposing that data in some way TeSS can consume
I guess we can put a 'search' icon that expands but
see github.com for a company with a budget dedicated to css/js as well, unfortuntely.
I'll see what I can do?
"train the trainer ASAP!!!" :)
Lol, yeah, ok, not an obvious place maybe. We opened an issue for it galaxyproject/training-material#1389 :)
maybe the tool could redetect the fastq type when creating the output? or maybe just needs some help text -- eg: "use edit attr > redetect". I like the first one better, less steps for the user
@bgruening Feedback from the end user running the bamtools extract tool and getting "fastq" instead of "fastqsanger" as the output (there data is fastqsanger). They do have an practical point here -- re-detecting datatype is not a batch operation -- making this all very tedious https://help.galaxyproject.org/t/convert-from-bam-to-fastq/1318/11?u=jennaj
ideas?
This got many thumbs up votes -- re: expanding batch operations on multiple datasets. Could be a different way forward: https://github.com/galaxyproject/galaxy/issues/3195#issuecomment-261427643
yes! please
I'll make a distinct ticket for it. Only found it because I've wanted it since at least 2016, lol
Yes, have been reviewing those. I'll make time to branch some of those out into individual ticket for discussion/action about best possible solutions. Might take me a while, but will get started. I might copy those comments off so can track them/link in derivative tickets. How to link back? Ok to just post directly to that thread and reference the original comment>
?
Ok, will do that. I'll make the "big" tickets in here https://github.com/galaxyproject/usegalaxy-playbook/, create new tags as needed, then make actual "fix" tickets where appropriate (iuc-tools, galaxy, etc). That repo can house all user feedback items -- as long as we tag them right -- too complicated to make yet another repo to track
Btw - make ticket here galaxyproject/galaxy#8013 and put on the list here https://github.com/galaxyproject/usegalaxy-playbook/projects/2#column-5163771
and use PJAs for changing the datatype
not ideal but this should work
@jennaj a workaround is to do this as a workflow
and use PJAs for changing the datatype
not ideal but this should work
good to know there's a workaround but I would not have known (and am not sure) how to do that, it doesn't seem very intuitive for users
^^ yeah, that is new-ish and involves a few steps. definitely wouldn't look good in the middle of a tuto. let's see how the discussion goes on that ticket. The more who want it, the more likely it is to get prioritized. Got many upvotes when embedded in that other ticket
I think the "operations on multiple datasets" option list is too sparce. much more we could do there, and it already would have a home -- no new GUI button or anything like that