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

Changing workflows on Galaxy #149

Open
spficklin opened this issue Nov 25, 2019 · 1 comment
Open

Changing workflows on Galaxy #149

spficklin opened this issue Nov 25, 2019 · 1 comment

Comments

@spficklin
Copy link
Member

If a workflow that has been integrated with Tripal changes on the Galaxy side, there is no notification to the Tripal site that something has changed, and it is possible to re-add the same workflow twice, after a changes has been made. We need a better way to handle changes.

@Ferrisx4
Copy link
Member

Determining whether a workflow has been updated can be accomplished by checking the UUID of the workflow, which changes every time a workflow is changed and saved. The ID of a workflow does not change.

We also need to consider the above case for the sake of reproducibility. In other words, if someone executes a workflow but later the workflow changes, there should be a way to indicate that the results were created with a prior version and a way to provide access to that prior version. From what I can tell, and from Galaxy Issue 6410, there is still work to be done on the Galaxy side to support this. At the current moment, the Galaxy API supports workflow versions, but the information provided is insufficient.

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