NoopDog
commented
1 year ago Regarding UX for this feture...
Our initial idea on the functionality for this was to show the empty list but also show the user the obsolete filter and let them dismiss it. Trying to develop this, we realized this requires, for ontology filters, for us to save the ontology term description along with the selected value in local storage when we save the filters.
One simplifying idea is to clear the obsolete filters for the users automatically. Doing so would free us from having to save the term name and value and simplify the implementation. Usually, we don’t “do things for the user,” but I wanted to check if this was an acceptable UX for this “obsolete filters” corner case.
To clarify, the user experience would be:
- Create a new collection. Add the Alzheimers dataset to the collection.
- Filter by Tissue: organ is brain and then tissue is entorhinal cortex.
- Create a revision of the new collection. Update the dataset to “All cells…“.
- Publish the revision.
- Go to the collections page.
- Instead of seeing “No Results” and no filters selected, we would detect that an obsolete filter was applied and silently.
The UX approach above was discussed and thought "ok" on our Aug 14, 2023, call with Harley, Brian, and Kuni.
brianraymor
jahilton
Description
In the updated curator experience, a curator can filter down to where a single row exists in the collections list, and then modify that single row so it no longer matches the filter. Once the update is processed the filter will show "no results" and the user will have to either clear the cellxgene session storage (which forces logout) or open the collections/datasets page in a new tab.
To reproduce
The status filter of "Revision" will be applied making the collection list show "No Results" but the filter will be missing from the filter selections on the left-hand filters ( the blue chip with "Revision") so you can't clear the "Revision" filter to get back to the full result set.