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

Add link to AIV reference history on Galaxy US #5395

Merged
merged 2 commits into from
Oct 4, 2024

Conversation

wm75
Copy link
Contributor

@wm75 wm75 commented Oct 3, 2024

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.

Also bumps tool versions used and adds a bit of explanation on how
phylogenetic trees can be visualized in Galaxy.
@wm75 wm75 requested a review from a team as a code owner October 3, 2024 11:30
@@ -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.
Copy link
Member

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?

Copy link
Contributor Author

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?

Copy link
Member

@hexylena hexylena Oct 4, 2024

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

bgruening
bgruening previously approved these changes Oct 3, 2024
@bgruening
Copy link
Member

@bgruening
Copy link
Member

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.

@davelopez
Copy link
Collaborator

Question more to @davelopez. Should we make those histories archived, so Wolfgang can not delete them accidentally or add new stuff to it?

That is one of the motivations for archiving histories yes.

@hexylena
Copy link
Member

hexylena commented Oct 4, 2024

@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!)

@davelopez
Copy link
Collaborator

Sure, every history API call will contain an "archived" flag telling you so: https://usegalaxy.eu/api/histories/0fc6b637aadbc8a2?view=summary

@hexylena
Copy link
Member

hexylena commented Oct 4, 2024

I was not familiar with the ?view=summary key before, interesting. What other views are available?

@davelopez
Copy link
Collaborator

davelopez commented Oct 4, 2024

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 keys:
https://usegalaxy.eu/api/histories/0fc6b637aadbc8a2?keys=name,archived

@hexylena
Copy link
Member

hexylena commented Oct 4, 2024

oh, very useful to know, thank you!

@bgruening bgruening merged commit dd4bb2c into galaxyproject:main Oct 4, 2024
3 checks passed
@bgruening
Copy link
Member

Sorry for derailing this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants