Harald_S

Some people expose a hierarchy in their tag naming schemes. See this earlier post from this thread: http://forum.evernote.com/phpbb/viewtopic.php?f=30&t=20719#p116181, for example. Again, not necessarily convenient, but possible.

Quite OK, one could tag each "subdirectory" accordingly so notes of that level will show up when clicking on the tag.

Drawback again: In a client visualizing the shared tag tree the hierarchy of the original is lost and not displayed. Also the introduction of tags by the co-users is not supported.

The issue becomes one of is it good enough.

It is, I made my mind up about that. I'm just trying to push the limits for greater acceptance by my colleagues where practicability within known concepts is an issue.

I usually put structure into my note titles. e.g "Hardware - Scanner - ...", "Evernote - Web -..", "Client - Project -.." etc.

Thanks for the proposal. You're right, flattening out the directory path into the title is a feasible workaround and probably my means of choice.

Nevertheless it's a bit of a drag with growing complexity and only of moderate elegancy ;-). Just imagine a little adjustment in "directory structure" leading to editing all of the titles.

Harald

The drawback on tag structuring in flat collections is that you only see the immanent structure by searching and not by showing.

If you want to share structured information, like projects/circumstances where the structure of presentation is part of the information itself

a) it forces you to put all information/notes into a single notebook, because there are no overall tags once shared

the structure within has to be outlined by a "keynote" or people won't know the structure inferred otherwise by obvious organisation

This means that Evernote generally is more applicable for sharing collections than constructions.

P.S. The concept of "inheriting" context by nesting entities of understanding is quite a real world model and natural, not so much just "old" thinking habit.