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

Issues on the Ingest-UI #1442

Open
libpitt opened this issue Aug 5, 2024 · 1 comment
Open

Issues on the Ingest-UI #1442

libpitt opened this issue Aug 5, 2024 · 1 comment
Assignees

Comments

@libpitt
Copy link
Contributor

libpitt commented Aug 5, 2024

  1. There is a brief flash of the login page on refresh of the ui. This can be quite noticeable when the page has been idle for some time.
  2. The filtering currently only filters what's been returned from the /search (i.e. current table results) and not reachable to search beyond that scope. Expected UX:
    a. If a user sets some filter, say Group Name, and then clicks SEARCH, this should return any entities with the user's set group name. This is possible by modifying the elastic search query to include filters.
  3. As with filtering, same goes for column sorting. It only sorts the results from /search
  4. User needs to click SEARCH to query beyond the scope of current result. Ideally, the user should be informed of this behavior
  5. Filter operators from the MUI's DataGrid component that are not being handled by the application should ideally be removed
  6. Clicking the CLEAR button returns No record found message, this should ideally return the default results.
  7. The query parameters (in the browser url field) aren't being handled by the application, but are being set in the url every time a user filters their search
  8. Directly visiting the url say: https://ingest.dev.hubmapconsortium.org/?entity_type=publication&keywords=lisa seems to not always redirect the user automatically.
  9. Missing spinner to indicate loading data

The attached video addresses some of these issues.
https://github.com/user-attachments/assets/a663273b-2821-42a3-92f1-b9792e74ff59

unused-operators

@yuanzhou
Copy link
Member

yuanzhou commented Aug 6, 2024

@libpitt Thanks for the list and we'll prioritize and make plans accordingly. @BirdMachine just a heads-up, no immediate actions needed as we are still finishing the documentation work.

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

No branches or pull requests

3 participants