-
Notifications
You must be signed in to change notification settings - Fork 905
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
Add link to AIV reference history on Galaxy US #5395
Conversation
Also bumps tool versions used and adds a bit of explanation on how phylogenetic trees can be visualized in Galaxy.
@@ -75,7 +75,10 @@ Instead, to save some time, you can copy an existing shared history on Galaxy Eu | |||
|
|||
> <hands-on-title>Prepare the Galaxy history</hands-on-title> | |||
> | |||
> 1. Open the [shared history](https://usegalaxy.eu/u/wolfgang-maier/h/influenza-resources) with pre-prepared INSAFlu reference data | |||
> 1. On Galaxy Europe, open the [shared history](https://usegalaxy.eu/published/history?id=0fc6b637aadbc8a2) with pre-prepared INSAFlu reference data. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a way to annotate this as metadata have you tried that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For zenodo data I know that, but for shared histories?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should add an FAQ for it, but, yes, they can be annotated. e.g.
input_histories:
- label: "UseGalaxy.eu"
history: https://humancellatlas.usegalaxy.eu/u/wendi.bacon.training/h/cs1pre-processing-with-alevin---input-1
answer_histories:
- label: "UseGalaxy.eu (includes AnnData to CDS conversion)"
history: https://humancellatlas.usegalaxy.eu/u/j.jakiela/h/monoce3-tutorial-workflow
date: 2024-03-04
Question more to @davelopez. Should we make those histories archived, so Wolfgang can not delete them accidentally or add new stuff to it? How should we handle those histories in the long run. |
That is one of the motivations for archiving histories yes. |
@davelopez if we can we easily tell from an e.g. API call (as anonymous external users) whether those histories are archived or not, we can add linting to ensure those histories are archived (it's a good point @bgruening!) |
Sure, every history API call will contain an "archived" flag telling you so: https://usegalaxy.eu/api/histories/0fc6b637aadbc8a2?view=summary |
I was not familiar with the |
Here is the list of views available to histories: https://github.com/galaxyproject/galaxy/blob/d18bc6855df1d168394778658cd108be67004650/lib/galaxy/managers/histories.py#L776 You can also get a specific set of fields using |
oh, very useful to know, thank you! |
Sorry for derailing this PR. |
Also bumps tool versions used and adds a bit of explanation on how phylogenetic trees can be visualized in Galaxy.
Most importantly, this will enable people to follow the tutorial on usegalaxy.org in addition to Galaxy Europe.
Agreed that this is sort of a quick fix and that the data in question should really live on zenodo, but I'm still in the process of figuring out the final shape of this tutorial.