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

BUG: Fix Tags filter menu #39

Closed
abelpink opened this issue Sep 16, 2024 · 5 comments
Closed

BUG: Fix Tags filter menu #39

abelpink opened this issue Sep 16, 2024 · 5 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request Low Priority

Comments

@abelpink
Copy link
Collaborator

The tags filter menu is currently only showing top-level tags and a count of how many items possess tags within that hierarchical level. E.g.,

Image

The expected behavior is to see terms listed that the items are actually tagging (not their category) and a count of how many times that term is tagged. E.g.,

Image

@abelpink abelpink added the bug Something isn't working label Sep 16, 2024
@abelpink
Copy link
Collaborator Author

You might be able to reference PCORnet documents for this since their tag filter is working as expected.

@aseyedia
Copy link
Collaborator

aseyedia commented Sep 20, 2024

The default options for the hierarchical search filter facet doesn't support this and I would probably have to intervene at the Java level or the Angular level.

@aseyedia
Copy link
Collaborator

I'm going to close this issue for now, feel free to reopen it as a feature request later, should you want to do this.

@aseyedia aseyedia closed this as not planned Won't fix, can't repro, duplicate, stale Sep 27, 2024
@aseyedia aseyedia pinned this issue Sep 27, 2024
@aseyedia
Copy link
Collaborator

@aseyedia aseyedia reopened this Sep 27, 2024
@aseyedia aseyedia added enhancement New feature or request backlog Unable to address for now. labels Sep 27, 2024
@aseyedia aseyedia removed the backlog Unable to address for now. label Oct 18, 2024
@abelpink
Copy link
Collaborator Author

Okay, so I think I understand why this is the way that it is. It's definitely not a bug nor is it ideal, but I think I can live with it. I'm going to close this ticket since I don't think it's worth fixing when we have other things to address.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request Low Priority
Projects
None yet
Development

No branches or pull requests

2 participants