Skip to main content
User Experience

Return to Question

tidied
Source Link
Erics
Erics
  • 9.4k
  • 6
  • 52
  • 78

which Which implementation for a dynamic hierarchy tree will show as much info as possible while still allow seeing the changes made in the background?

I'm in the middle of building a search engine website for a specific corpus. we've

We've already implemented most of the menus and the structure of the website. recently we got some feedback that forced us to implement a feature that we haven't thought about.

Here are the categoriesthe categories (which are basically classifications): http://web2.wipo.int/ipcpub/#refresh=page youyou can play with the different levels - click on "A", see that it has the title "HUMAN NECESSITIES", then click "A01", it has the text "AGRICULTURE; FORESTRY; ANIMAL HUSBANDRY; HUNTING; TRAPPING; FISHING", under "A01" you can see that there are many more sub-classes ("A01B", "A01C", "A01D" etc') that have more sub-classes under. each class has a "title" which I also want to display.

asAs you can see, at any time the user can go back to the upper level and basically know where he is in the path.

aA search may return results from different classifications. I want the users to be able to filter results by classifications. at first, I plan to show the root classifications related to the search results on the main results page with a count of the results under that classification (I still don't know where it will shown in the page). each result is linked to a sub-sub-classification, each result may be linked to several sub-classifications.

afterAfter a user performs a search we will gather and display all the root classifications related to that search with the number of results under each class. the user will be able to choose a classification, then he will be able to choose it's sub and so on while still maintaining the path.

theThe link above shows a solution that we can't use, it takes too much space and we want to dynamically refresh the results set on every click, narrowing down (filtering) the results, so whenever a user click or "goes into" a sub class he will be able to see the change on the results page.

In my imagination I think of a semi-transpernttransparent rectangle that "floats" on top of the results, it can be dragged any where on the screen, it has a 50% transparency and when clicking on a class it will open a list of sub-classes, then collapse the upper levels so the user will be able to go back.

theThe solution that comes to my head for the titles problem is that titles may be shown as a 'tooltip' on mouse over, but the fact that tooltips are only shown when hovering on a class it may be difficult to remember which title corresponds to the matching class.

hereHere is a wireframe of the website:

thisThis is how I imagine it: search-results-with-filter

theThe problems:

isIs that the right solution?

which implementation for a dynamic hierarchy tree will show as much info as possible while still allow seeing the changes made in the background?

I'm in the middle of building a search engine website for a specific corpus. we've already implemented most of the menus and the structure of the website. recently we got some feedback that forced us to implement a feature that we haven't thought about.

Here are the categories (which are basically classifications): http://web2.wipo.int/ipcpub/#refresh=page you can play with the different levels - click on "A", see that it has the title "HUMAN NECESSITIES", then click "A01", it has the text "AGRICULTURE; FORESTRY; ANIMAL HUSBANDRY; HUNTING; TRAPPING; FISHING", under "A01" you can see that there are many more sub-classes ("A01B", "A01C", "A01D" etc') that have more sub-classes under. each class has a "title" which I also want to display.

as you can see, at any time the user can go back to the upper level and basically know where he is in the path.

a search may return results from different classifications. I want the users to be able to filter results by classifications. at first, I plan to show the root classifications related to the search results on the main results page with a count of the results under that classification (I still don't know where it will shown in the page). each result is linked to a sub-sub-classification, each result may be linked to several sub-classifications.

after a user performs a search we will gather and display all the root classifications related to that search with the number of results under each class. the user will be able to choose a classification, then he will be able to choose it's sub and so on while still maintaining the path.

the link above shows a solution that we can't use, it takes too much space and we want to dynamically refresh the results set on every click, narrowing down (filtering) the results, so whenever a user click or "goes into" a sub class he will be able to see the change on the results page.

In my imagination I think of a semi-transpernt rectangle that "floats" on top of the results, it can be dragged any where on the screen, it has a 50% transparency and when clicking on a class it will open a list of sub-classes, then collapse the upper levels so the user will be able to go back.

the solution that comes to my head for the titles problem is that titles may be shown as a 'tooltip' on mouse over, but the fact that tooltips are only shown when hovering on a class it may be difficult to remember which title corresponds to the matching class.

here is a wireframe of the website:

this is how I imagine it: search-results-with-filter

the problems:

is that the right solution?

Which implementation for a dynamic hierarchy tree will show as much info as possible while still allow seeing the changes made in the background?

I'm in the middle of building a search engine website for a specific corpus.

We've already implemented most of the menus and the structure of the website. recently we got some feedback that forced us to implement a feature that we haven't thought about.

Here are the categories (which are basically classifications): you can play with the different levels - click on "A", see that it has the title "HUMAN NECESSITIES", then click "A01", it has the text "AGRICULTURE; FORESTRY; ANIMAL HUSBANDRY; HUNTING; TRAPPING; FISHING", under "A01" you can see that there are many more sub-classes ("A01B", "A01C", "A01D" etc') that have more sub-classes under. each class has a "title" which I also want to display.

As you can see, at any time the user can go back to the upper level and basically know where he is in the path.

A search may return results from different classifications. I want the users to be able to filter results by classifications. at first, I plan to show the root classifications related to the search results on the main results page with a count of the results under that classification (I still don't know where it will shown in the page). each result is linked to a sub-sub-classification, each result may be linked to several sub-classifications.

After a user performs a search we will gather and display all the root classifications related to that search with the number of results under each class. the user will be able to choose a classification, then he will be able to choose it's sub and so on while still maintaining the path.

The link above shows a solution that we can't use, it takes too much space and we want to dynamically refresh the results set on every click, narrowing down (filtering) the results, so whenever a user click or "goes into" a sub class he will be able to see the change on the results page.

In my imagination I think of a semi-transparent rectangle that "floats" on top of the results, it can be dragged any where on the screen, it has a 50% transparency and when clicking on a class it will open a list of sub-classes, then collapse the upper levels so the user will be able to go back.

The solution that comes to my head for the titles problem is that titles may be shown as a 'tooltip' on mouse over, but the fact that tooltips are only shown when hovering on a class it may be difficult to remember which title corresponds to the matching class.

Here is a wireframe of the website:

This is how I imagine it: search-results-with-filter

The problems:

Is that the right solution?

Tweeted twitter.com/#!/StackUX/status/397027966951387136
edited tags
Link
YSY
YSY
  • 153
  • 2
Source Link
YSY
YSY
  • 153
  • 2

which implementation for a dynamic hierarchy tree will show as much info as possible while still allow seeing the changes made in the background?

I'm in the middle of building a search engine website for a specific corpus. we've already implemented most of the menus and the structure of the website. recently we got some feedback that forced us to implement a feature that we haven't thought about.

We are looking for a way to create a new filter in our results page. this filter will allow users to choose "categories" to filter the search results. this categories filter will display about 8 root categories which have many sub-categories, which have few more sub-categories, there are about 5 levels (sometimes the lowest levels may have sub children).

Here are the categories (which are basically classifications): http://web2.wipo.int/ipcpub/#refresh=page you can play with the different levels - click on "A", see that it has the title "HUMAN NECESSITIES", then click "A01", it has the text "AGRICULTURE; FORESTRY; ANIMAL HUSBANDRY; HUNTING; TRAPPING; FISHING", under "A01" you can see that there are many more sub-classes ("A01B", "A01C", "A01D" etc') that have more sub-classes under. each class has a "title" which I also want to display.

as you can see, at any time the user can go back to the upper level and basically know where he is in the path.

a search may return results from different classifications. I want the users to be able to filter results by classifications. at first, I plan to show the root classifications related to the search results on the main results page with a count of the results under that classification (I still don't know where it will shown in the page). each result is linked to a sub-sub-classification, each result may be linked to several sub-classifications.

after a user performs a search we will gather and display all the root classifications related to that search with the number of results under each class. the user will be able to choose a classification, then he will be able to choose it's sub and so on while still maintaining the path.

the link above shows a solution that we can't use, it takes too much space and we want to dynamically refresh the results set on every click, narrowing down (filtering) the results, so whenever a user click or "goes into" a sub class he will be able to see the change on the results page.

My thoughts

In my imagination I think of a semi-transpernt rectangle that "floats" on top of the results, it can be dragged any where on the screen, it has a 50% transparency and when clicking on a class it will open a list of sub-classes, then collapse the upper levels so the user will be able to go back.

The problem is that titles can be very long and the path can be too deep to show on one screen while still be able to see and interact with the results (there are several functionalities for each result on the results page).

the solution that comes to my head for the titles problem is that titles may be shown as a 'tooltip' on mouse over, but the fact that tooltips are only shown when hovering on a class it may be difficult to remember which title corresponds to the matching class.

what am I looking for?

  • a compact solution
  • clean responsive interface (let people know that the "box" is responsive)
  • allow users to navigate easily thru the tree (see the whole path)
  • display the titles
  • show the results changing dynamically in the results block
  • the ability to choose 2 root nodes and walk into them in parallel (nice to have, not a must)

here is a wireframe of the website:

search-results-wireframe

this is how I imagine it: search-results-with-filter

the problems:

  • how to show the sub-classes but keep the box's size rational?
  • after the user clicks on one of the classes, where should we display the sub-classes list? (under the father node? or on the right?)
  • the users should be able to see the results updated after each filter selection

is that the right solution?

My hope is that I will be able to use an already developed library and customise it to my needs.