-
Notifications
You must be signed in to change notification settings - Fork 172
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
Filters and sorts for datastore import status dashboard #3637
Comments
I think we decided #3714, which adds a UUID filter, was enough for now. |
Re-opening, we do want to add this if possible. The way we store some of this info as JSON and not columnar data makes some of this hard. Title will probably be the easiest. |
Based on spike 19023, we split this out into the easy bits and the hard bits. Low effort:
High effort:
|
FWIW I think this and #4332 suggest we really need a new approach to the dashboard. I think somehow it needs to be based on an array of resources that the metadata is derived from, not a list of datasets that we then inspect for resource/import info. Or at least to find some way of capturing a bit more in DB columns so that we are not dependent on data trapped inside JSON. Not saying we can't make some of these improvements on top of the existing approach but we we may be kind of at the limits of what we can do here. |
The user and title filters aren't that hard to implement as things are now, which is why I separated them out. In an ideal world this would be a view in Views and we could mix and match as desired. Sorts would then be a freebie if the data were represented by a views handler. |
Usually you are looking for a specific dataset when you come to the dashboard. Add:
The text was updated successfully, but these errors were encountered: