Thursday, April 2, 2009

The Taxonomy browser visualization #1 - Tree Lists

Hi, my name is Sergio Alvarez Leiva and this is my first pos at biodivertido, Finally. I'm part of Vizzuality and work as Interaction Designer for GBIF among others. I will mainly be posting about Interaction Design, UX and Design in general, althought I'll try to post about Front.end developing a little. I hope you find it interesting.

Since I began designing for Biodiversity data, I've encountered lot of interesting challenges related to the size of the datasets .
Maybe, one of the hardest challenges is designing a taxonomy browser visualization. The taxonomy browser can represent up to 1.7M names, with nodes with more than 200 childs. That makes it complicate in terms of interaction design and performance.
I will write in a series of post my impressions on different techniques we have been experimenting:

In this first post I'm going to talk about tree list visualizations, but before I get into details, I'd like to talk a little about generic concepts that might be applied to all the visualizations. There is a lot of bibliography about trees out there, but let me introduce here my own "easy" concepts.

When browsing a tree you need to know where you are and what is around you, thats parent and brothers and in general this is called Contextualization. Then you need to be able to find the childs, thats Discovering. All this needs to be easy to do, Usability and UX, and finally must be easy to integrate with the application, Easy integration.

On those terms, the tree list visualization presents some advantages and disadvantages.

- Contextualization: Maybe the list visualization is the most standard way to solve this problem. The tree lists lets the user discover the whole tree by clicking in the different nodes. But the problem is the vertical size that the tree gets when the user deployes a node (This is an integration problem too). When the user will have deployed more than 3 levels, he will have to use the vertical scroll, and probably, this action will make the contextual information (parent nodes and "brothers") out of the visible screen area.

This problem could be solved implementing some variations in the Tree list; We could hide all the nodes not related to the selected child and get more space for view only the important nodes.

-Poor UX : "Discovering biodiversity". We have to involve the users in our play and invite they to discover more and more. I think the Tree Lists are a little boring...we need more action!

- Usability: This visualization is pretty used and the users will understand how it works quickly. On the other hand, I think that in a Tree list is not so easy to find the desired node - the users would have to deploy a lot of nodes, and scroll a lot too, before find their objective. Maybe would be positive for this point to implement a search box. It might depend of the data size.

Conclusion; We've a standard visualization that lets us to implement a Taxonomic browser in a lot of different situations. I think this is not the best solution that we could implement, but its true that we could use this always. 
 

5 comments:

Nick said...

Can you expand the acronym "UX"? I'm not familiar with it.

Cheers
Nick (Atlas of Living Australia)

Sergio Alvarez said...

Hi Nick,

UX is the acronym of User Experience.

User experience is sometimes conflated with usability, information architecture (IA), and user interface (UI) design.

User experience design incorporates most or all of the above disciplines to positively impact the overall user experience a person has with a particular interactive system.

I hope you like the post.
Cheers.

Ryan said...

We are working on similar problems ourselves with the OntoSpecies project (http://ontospecies.ubio.org). It began as an exercise in Javascript and CSS to try to lay out a tree in a fluid, slightly more humane manner, now trying to evolve it into a fully usable taxonomy browser with search, common names, and more...

ponytail said...

Why not consider a hyperbolic tree browser? The big advantage is that all of the content is available at once in screen real-estate that need not change. With too many node some intelligent loading would have to be considered, but it still seems a better visualization mechanism than the linear tree.

ponytail said...

Forgot to add an example for the hyperbolic tree browser. An open source version can be found at http://hypertree.woot.com.ar/.