search

galaxyproject / galaxy

Data intensive science for everyone.
https://galaxyproject.org
Other
1.35k stars 979 forks source link

Allow Storage Management by Quota Source and Object Store #17447

Open jmchilton opened 5 months ago

jmchilton commented 5 months ago

https://github.com/galaxyproject/galaxy/pull/17437 adds the ability to assign datasets to other object stores (when "safe") and gracefully swaps around the quota seemingly.

But it operates one dataset at a time and it is not going to be clear to users what dataset is where if they start aggressively using these features. I think augmenting and extending the storage overview components could be a good way to expose some of this to users quickly:

My thought on some entry points:

Screenshot 2024-02-09 at 9 23 22 AM

Clicking the Quota Links would bring you to like the History Overview page but it would be aggregate across histories.

Clicking the manage by Object Store at the bottom would bring you a break down of your object store IDs and what is stored at them. Clicking a particular Object Store would bring a breakdown of dataset for that object store like the History or new Quota view described above.

My thoughts on navigating datasets:

I like the minimalism of the History Overview so maybe keep it like the default landing but add an advanced options link that adds filters for quota, object store, and deleted status.

This is really ugly but functionally if we could collapse it to a little bar or something as clean as what is there already:

Screenshot 2024-02-09 at 9 39 28 AM

I think that navigability is good but I'm not sure it helps batch moving things (or batch deleting or purging for that matter). Maybe for certain combinations of filters we could add batch move, delete, and purge options to these pages? Or maybe in addition to the graphs on these pages we could have a little multi-select tabular view of the datasets at the bottom of the page that allows these batch operations?

davelopez commented 5 months ago

Awesome idea! This functionality fits perfectly there. We can explore different ways of enabling multi-selection for batch moving/deleting/etc and see what works best.

martenson commented 2 months ago

It would be nice to use names instead of IDs for the stores and maybe even consider unifying the language (quota source, storage source, disk quota and disk usage are all used here)