David López

I'm going to make `purged` and `archived` histories able to be set as current and then restrict the UI options where appropriate. I can see the value in it. But...

Switching to non-active histories should be possible now with https://github.com/galaxyproject/galaxy/pull/18234 Regarding extracting a workflow out of a purged history that is not working, we probably should create a new issue...

> And maybe we should do this via the API ? I'm happy to move this to the API as a FastAPI endpoint. But it wouldn't be correct to target...

OK, thanks! I will then do the minimal fixes in the existing client controller for `24.0` and follow up on `dev` (after merge) replacing it with the new API :+1:

Should be fixed in https://github.com/galaxyproject/galaxy/pull/18200

> let's meet with @davelopez and discuss it further. Thanks! I'm not an expert here... but maybe we can add something like this to `lib/galaxy_test/base/populators.py`: ```python # Disclaimer: an AI...

I talk to @itisAliRH and we will push this to the next release so we can properly discuss it later.

So the point where we are missing the `user_context` is here: https://github.com/galaxyproject/galaxy/blob/c2438b2f06b92bc7169e5974f962de41e10cbc7b/tools/data_export/export_remote.py#L35 However, I'm failing to see how I can access the requesting user in the tool script to build...

This should be possible now using the new way of integrating Zenodo and Invenio-based repositories in combination with this fix https://github.com/galaxyproject/galaxy/pull/19768. There is a new blog post covering this approach...

It should be fixed in https://github.com/galaxyproject/galaxy/pull/19215, thank you!