I have been hunting through this thread and the suggestions linked to from it on-and-off for a year or so, hoping to find out how I can use tags to get the shelf/notebook/section/page hierarchy that I need. It seems to me that those espousing tags as doing everything that can be needed are focussing on *search* rather than *browse* capability. That's fine if I want to search for a page with a particular comment on it, but less useful if what I want to do is read sequentially through a set of notes - for example, if I want to revisit my notes from part of a project or a course I was working on a while ago.
The model in my head of what I want is to have:
SHELF - Shelves (or "stacks" in EN terminology) corresponding to, for example, "Professional Development", "Projects", "Domestic", and so on
NOTEBOOK - Within shelves (stacks), notebooks corresponding to, for example", particular professional development courses I have taken, projects I have worked on, etc.
SECTION - Within a notebook, I want sections for the parts of the course - for example, in a notebook for a Machine Learning course, I might have sections of Introduction, Linear Regression 1V, Linear Regression MV, Logistic Regression, Regularisation, etc
NOTE - Within each section I want to put my actual notes, with a logical order
So, if I want to refresh myself on Logistic Regression, I go to the "Professional Development" shelf, take the "Stanford Machine Learning 2014/15" notebook, turn to the "Logistic Regression" section, and read through the notes there in sequence.
I am unclear how to use the EN tag hierarchy to do that. I have tried various ways, but I end up having to do messy clumsy things of going via a search form, having to remember tags I used these things when I saved them, and then trying to guess what order to look at the search results in to get the logical order that part of the course happened in. It seems to me that it is easy an obvious how to browse to things in hierarchical storage metaphor, but that tagging and searching doesn't fit this particular access need.
(Don't get me wrong - tags are great, and I can use tags to meet subsidiary *search* requirements I have, but I can't make it fit well to this more common access need I have).
Can anyone tell me what I am doing wrong here, and how to get what I want using tags?