[QUESTION] Do you have any plans for a 'Refiner' filter type for taxonomy fields?

[schaeferalexander]

Version used
Ex: 1.3.2

Question
Do you have any plans for a 'Refiner' filter type for taxonomy fields? Will there be a future release with the 'Refiner' filter type for taxonomy fields for filter webpart or do you will not implement this feature?

Additional context
In one of our customer projects we want to use your solution. The main feature the customer needs there is the hierarchical view of taxonomy field filters depending of the term store structure. In the current version "filters with empty results" are displayed for the user and the values count is not available - the expected behavior for static filters, I know. Unfortunately it is very disappointing for the user experience. It would be great to know how your product roadmap looks like and if the customers requirement is part of it.

I hope this is the right channel to ask questions like this.

[Laul0]

Hi @schaeferalexander,

Yes, this is the good channel to ask questions 👍🏻

We already provide a Taxonomy filter based on the term store. I think this is what you are looking for: https://aequos-solutions.github.io/modern-data-visualizer/usage/data-filters/#taxonomy-picker-template-configuration

[schaeferalexander]

Hi @schaeferalexander,

Yes, this is the good channel to ask questions 👍🏻

We already provide a Taxonomy filter based on the term store. I think this is what you are looking for: https://aequos-solutions.github.io/modern-data-visualizer/usage/data-filters/#taxonomy-picker-template-configuration

Hi @Laul0,

Thank you for the answer. Yes, this is the filter I am talking about and we want to use for our customer.

The issue is, that the values of the filter are still displayed even there are no search results available with the value:

The expected behavior is that the filter values are not visible when there are no search results which are tagged with them:

[Laul0]

This is the expected behavior of this refiner.
As you well explained, the values of this kind of refiner are based on the Term Set and not on the results.

Currently, no improvement is planned to hide taxonomy terms or count items based on the search results.
We will add the suggestion to our internal backlog to keep track and maybe add this feature when the most priority issues will be done.

By the way, you can use choice refiner and manage the template.

• Set your taxonomy field with full path term
• From the filter Template, split the values by the default separator, and arrange the display as hierarchical terms

I didn't try it myself, but it can be work

[schaeferalexander]

Hi @Laul0,

thank you for the idea with the alternative solution (full path term and rearranging the terms by splitting them). It seems to work so far. There are only two other effects where we working on now.

• In the UI of the selection dialog the full path is shown because of the setup. What is not very pretty, but not really a show stopper
• The customer environment (and the solution) is multilingual. When using the full path configuration, the path of the filter is displayed in the default Term Store language and not in the current browser language.

Please inform me when you plan to implement the feature (hide taxonomy terms and count items based on the search results) in the Aequos solution.

[JoeAyre]

Hi @schaeferalexander, @Laul0,
Could you let me know how I would go about doing the following?
From the filter Template, split the values by the default separator, and arrange the display as hierarchical terms
Thanks,
Joe

[Laul0]

HI @JoeAyre,

Currently, the only way to get a hierarchical filter is to use a taxonomy picker.
The taxonomy picker is not bidirectional - in other words, the visible filters from the Taxonomy filter do not depend on the used terms from the Visualiser/results. It is by design.

Suggestion: If I had to create a hierarchical filter (not a deep one), maybe I would try to use a field with this kind of value: Level 1/Level 1.1
Then, create my own filter and split filter values to build a hierarchical one.

I hope this information will help you