changing number associated with dataset in a history

Question: changing number associated with dataset in a history

2.2 years ago by

United States

why can't we edit numbers of datasets (jobs) in a history. This is almost a deal killer on large datasets where individual jobs fail. It is a problem because you cannot go back and sync chronology with outputs for next steps in the pipeline so you end up with a bunch of crib sheets to try and track workflow. thanks, Nate

number history galaxy organization dataset • 469 views

ADD COMMENT • link •

modified 2.2 years ago by Jennifer Hillman Jackson ♦ 25k • written 2.2 years ago by nate.robinett • 10

2.2 years ago by

Jennifer Hillman Jackson ♦ 25k

United States

Jennifer Hillman Jackson ♦ 25k wrote:

Hello,

Changing the dataset numbers alone will probably not help with this issue. Renaming outputs based on the input dataset name can help some (possible within a workflow, and default output dataset "names" from many tools). Copying datasets to a new history, or deleting old ones (intermediate files, or failed runs, or other dead-ends) are other current options. The datasets are renumbered when you copy them to a new history. But none of these really address how to view the bigger picture in a complex history.

Providing a simple way to view dataset associations/provenance is an enhancement feature with great interest within both the Galaxy dev and user community. More developments in this area are planned. I don't think there is a specific enhancement ticket for this yet to share for you to follow, but either I or someone from our team/community will add one to the reply should one already exist (and I missed it) or one is created near-term.

Thanks for the feedback! Jen, Galaxy team

ADD COMMENT • link written 2.2 years ago by Jennifer Hillman Jackson ♦ 25k

Similar posts • Search »