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

Option to decide default filtering for Artifacts page #32

Open
timtreis opened this issue Jan 28, 2025 · 3 comments
Open

Option to decide default filtering for Artifacts page #32

timtreis opened this issue Jan 28, 2025 · 3 comments
Labels
enhancement New feature or request

Comments

@timtreis
Copy link

Description of feature

Hey y'all,

we just noticed that there are now certain filters that are active by default, f.e. is_latest - great! Do we have some control over this? Ideally we could f.e. always just subset Data Format to SpatialData

cc @zimea

@timtreis timtreis added the enhancement New feature or request label Jan 28, 2025
@falexwolf
Copy link
Member

We want the ability to do this and it's quite high up on the priority list, but it will still take a month or longer depending on how much we can accelerate now with the bigger team (FYI @awgaan).

Is there a simple way in which we can make you happy before this is fully configurable by instance admins? I imagine that simple logic for scverse/spatialdata-db could be added to the frontend if you tell us the default values you want for it.

@timtreis
Copy link
Author

timtreis commented Jan 29, 2025

It seems that this is passed in the URL, could we request this to be customised? I guess we don't really need to adjust it on the fly

@falexwolf
Copy link
Member

could we request this to be customised

That's what I tried to suggest. ☺ -- You tell us the defaults you want beyond "data format = SpatialData" and we'll make that happen for the spatialdata-db instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants