minh-pham1
commented
6 days ago Will raise a ticket with our Alvin and our design team about the official design decision.
As far as I know, I do believe that we provide a very strict list of filters/tags/categories for each product to label all of their documents and APIs for quick filtering. This way we can have a succinct list of filters for all users to utilize within Catalog/Search to find a wide variety of options for the category they need if they don't already know.
The main issue we have with custom tags is if every product has different, unchecked tags on every document. A user looking at a filter list might get daunted by the long list and trying to decipher the difference between one product using the filter Banking for SMB and another maybe writing SMB Banking vs a third just saying Small Medium Business. Just a sample case from my understanding of why the tag list is the way it is.
As mentioned though, I'll still create the ticket and see whether there are any changes we may want to make in this regards.
Context
Currently search tags are coded to the tenant and all documents have the same tags, these are not useful from a navigation and usage perspective. Original Ticket https://github.com/Fiserv/Support/issues/337 and prior request on tag filtering https://github.com/Fiserv/Support/issues/146
Solution
There should be a default set of tags that relate to the search options/filters. Then additionally the tags on the individual articles should be used to override or add to the default tags when available.
Alternatives
n/a
Additional Context
Similarly when you click on the tag in the search or in the article it should being a set of search results containing that tag.
Region
No response