Per your request I have reviewed the linked issues and created a
list of things I think can be done that are relatively easy to improve
the current situation here
There are a lot bigger things that need to be done as well - but they
are very high level and they seem to be fairly controversial and
relatively difficult to implement.
On Thu, Sep 29, 2016 at 4:03 AM, Ziphozakhe Mashologu <zipho(a)sanbi.ac.za> wrote:
In using Galaxy, I would like to be able to keep track of the input dataset
name down the analysis chain.
This is a similar if not the same issue raised by Eric in
, to which he proposes in
the context of a workflow that, "the rename dataset action should support
usage of all the dataset names from Input Dataset elements, rather than just
input files to the particular tool." Please see the issue for more details.
There are other similar issues raise scattered all over regarding the same
1. Ability to name datasets using the element identifier:
2. Ability to define the collection name in a workflow:
3. Name datasets according to both collection name and element identifier:
1. Renaming using the input from paired dataset collections:
I have created a github issue regarding the above, in effort to try and
consolidate all these related above issues.
Can we use the above issue to discuss the best approach on these issues,
point out work being done on the area and perhaps define clear milestones
Galaxy Devs please provide me some guidance to best tackle this.
(particularly of tracking the input dataset names along the analysis chain).
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:
To search Galaxy mailing lists use the unified search at: