-
Notifications
You must be signed in to change notification settings - Fork 80
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
Collections Page - Filter by Content Type #1168
Comments
I noticed that when filtering to only a problem subtype, when there's a blank problem, the count / problem type match is inconsistent. In the screenshot above, I selected the "Checkboxes" type, which has one match. The parent "Problem" type (tagged with two matches) is selected as well, and both the problem components are selected. I would expect this to only show the 1 matching problem. |
^ This is a weird edge case when your library only has a single type of problem, alongside blank problems. The issue is that whenever you check all the available sub-types of problem, it will include blank problems as well, since it interprets that the same as "all problems". We could address this in the future by explicitly adding "Blank Problem" as a sub-type of problem. But there are other random sub-types as well that won't show up. |
@jmakowski1123 @lizc577 @sdaitzman @marcotuts This is ready for AC testing on the sandbox |
Looks good! |
If a Collection has content populated in it, users can filter that content using Content Type.
See implementation details for filtering by Content Type at the Library level: #1049. A similar implementation needs to happen at the Collection level, but the filtering is limited to content contained within the Collection.
The text was updated successfully, but these errors were encountered: