Although it's hierarchical in the sense that taxonomies/departments it selves are grouped by a parent, content items are matched to an individual taxonomy/department.
This means you're basically euhm... well you know...
There are arguments for and against this way of implementation, but on this case I'm on Steve's side.
Pro: For instance on a 'department' level you might have a parent group called 'drilling machines' and a child department called 'drilling bits'. Naturally when viewing the parent group you don't want to see products from the child group (drilling bits).
Against: For instance the taxonomy 'service industry' might hold subcategories like 'legal', 'consulting firms' and 'ad agencies'. In this case all elements in the child nodes should be part of the parent node as well...
When using Taxonomies, you'd expect to have a choice whether 'child elements' should be included into the result. Currently there's no way to do this...
For it (as a developer to work) I'd first have to retrieve all child nodes. Then for each child node add the results to the 'parent resultset' and loop through all the individual child nodes one at a time. (Time and data consuming).
For Sitefinity to make this work, would be to alter the query a bit based on a checkbox.
- not include children > do the same as now.
- include children > change the query to "where parentid=".." instead of id="..."
This is a modification that's so small, but would be so helpful, it shouldn't even deserve a PITS number ;) because it's not a bug or a feature request but in many cases a time saving necessity.