ChrisCN wrote:how can this method build up a hierarchy deeper than 2 levels?
Well, you made me spend even more time on this. I made up a more complex example.
Have 2 notes with the following tagsprojects project-A customer-A software
projects project-B customer-A software
In its first level this would result in:projects/
projects/project-A
projects/project-B
projects/customer-A
projects/software
customer-A/
customer-A/project-A
customer-A/project-B
customer-A/projects
customer-A/software
software/
software/project-A
software/project-B
software/projects
software/customer-A
The second level:projects/
projects/project-A
projects/project-B
projects/customer-A/
projects/customer-A/project-A
projects/customer-A/project-B
projects/software/
projects/software/project-A
projects/software/project-B
The example is made up for "projects" only.
The third level:projects/
projects/project-A
projects/project-B
projects/customer-A/
projects/customer-A/project-A
projects/customer-A/project-B
projects/customer-A/software/
projects/customer-A/software/project-A
projects/customer-A/software/project-B
projects/software/
projects/software/project-A
projects/software/project-B
projects/software/customer-A/
projects/software/customer-A/project-A
projects/software/customer-A/project-B
The example is made up for "projects" only.
ConclusionWhen looking at this example, to me 2nd- and 3rd-level don't add a real benefit. I think i would be happy with the results of the first level. It shows my main concern. Building up a tag-tree, that allows to look up the same data from different perspectives. This can be achieved by an intelligent tag-explorer, without the need to have the user build up such hierarchys.
ChrisCN wrote:what about the hierarchies we have (predefined) - can they join in? (or are they of no additional use here?)
Well, maybe others can use their brain too

Imo, i would ignore them in the tag-explorer, since they build up their own hierarchy.