Building Efficient Node Hierarchies

Organized hierarchically, nodes show the shape of the emerging categories, the concepts in which the data are being analyzed.

A well organized hierarchy of tree nodes or cases should:

The simple rule is if a node obviously "fits" in your conceptual tree, place it there. If it doesn't, don't force it—create it as a free node until its relation to other nodes becomes clearer.

Structuring Your Node Hierarchies

Node hierarchies are usually best kept coherent and concise. Ensure that conceptually related categories are kept together and unrelated categories apart.

The most common problem hierarchy is one in which a node has been made for every possible combination of categories, rather than coding the same passage at multiple nodes.

If you are unsure whether a category fits into an existing node hierarchy, ask whether it is a sort of the category in question. If it is, it should create a child node within that tree, if it is not, consider whether it should be part of another tree or exist independently (i.e. as a free node).  Similarly, if you notice that a node name appears more than twice within your trees, you may need to create it as its own node.

In the Volunteering Sample Project  

 

Related Topics