OVPdev

3 hours ago, jefito said:

First, your question presupposes that there are levels of nesting associated with a project that are required for finding things. What do they represent? If your question isn't just rhetorical or hypothetical, then more information would be needed as to what the levels entail. Hierarchy might not be necessary for your use case, despite your assumption that it is.

For me, the first step would be to create a project tag, and apply it to the 50+ notes. If there wasn't one already, I'd create a project summary as well; that would be my starting point into the project. So right there, you can now easily filter your note database down to that set of notes, across any notebook structure you care to construct; one likely possibility is that you' dedicate a single notebook to the project. That would make sharing with other users easier.

I think you may have a mistaken assumption here: Selecting a tag doesn't automatically show you all of the notes that have tags that are children of the original tag, unless they also have the original tag (note that the Windows Evernote client _does_ allow you do do this as an option, but I thought that it was awkwardly implemented, and not particularly useful to me).Again, more information would be required before I would say whether doing that was a good idea or not.

Of course, if you're just setting up a straw man here, rather trying to work better in Evernote as it is today...

that particular chain of replies started with this comment: 

@DTLow  tried to convince me that tag hierarchy is good for that type of problem, and instead of explaining how to actually navigate and find notes, he explained how to create structure.

and for some reason, people who don't face the problem repeatedly impose the same solution again and again without testing it at work.

My point is, that a note with internal links is a lot better than tag hierarchy for that type of problem

10 hours ago, DTLow said:

Not just projects; on a Mac, we can create a hierarchy for organization  (also Windows)
- 2  notebook levels
- unlimited tag levels

>>Imagine you have a project with 50+ notes and nesting 7+ levels, how would you navigate?   ...
How would you reach the target note?

For navigation, we can display the notebook and tag trees in the sidebar
The screenshot shows the tag tree with  with 7 levels.

The notebook tree is similar but less effective; we can only have two levels. Hence  the above feature request

 

You didn't answer the question:

How would you reach the target note which is near the root level using tags, if there are a lot of notes in children tags?

1 hour ago, DTLow said:

I work on projects.  I'm not clear on how this relates to nesting/sub notebooks.

Hierarchical organization is a great featiure.  I  use it on Evernote/Mac to keep my tags (350+) organized.
I have minimal notebooks (6) so organization isn't a big issue for me.  The Stacks feature works well.

it's hard to believe you, you act like you never work like that.

so you are telling me that using tags you can make a big, deep hierarchy for working on big enough projects.

Imagine you have a project with 50+ notes and nesting 7+ levels, how would you navigate? 
You click on a tag to see 3 notes inside, and what would you see? A mess, notes inside all nesting tags, 20 - 30 notes instead of only 3 that actually inside. 
How would you reach the target note?

5 minutes ago, DTLow said:

I work on projects.  I'm not clear on how this relates to nesting/sub notebooks.

Hierarchical organization is a great featiure.  I  use it on Evernote/Mac to keep my tags organized.

Read my post. It's clear you haven't read it. You just replied.

I believe there are two categories of people: those who work on projects using Evernote, and those who don't.
And the last ones sincerely don't understand why is the feature they don't need is needed for anybody.
in my opinion, http://theguide.sourceforge.net/ had the best hierarchical structure view and the user experience for working on projects.

When you write a note, at some point you might need a deeper structure, so you create a note inside a note, and each of them has a content.

Differences compare to tags:

• notes don't change the order based on recency or name, only by user explicit actions. hence a user can leverage visual memory for better navigation
• only one parent, so I don't need to remove the old tag, assign the new one, and it's not possible to make a mistake during these actions 
• I can see all the notes inside a parent in the same view, so again I can use my visual memory to the fullest extent
• any parent can have a content, so you can start with the main idea and detail it with child notes
• Evernote parent tags contain everything that children and children of children contain, therefore I have to click on all the tags lower on the hierarchy, remember all the notes and compare what I've remembered with what Evernote shows me to finally find out what are the actual children.

Tags are really bad for this purpose. I use a note with structured references instead. 
Don't get me wrong, tags are good but not for that.

The better solution for adding this type of view is to make it as a separate database or hidden note with information about references and structure. When you turn it on it's empty, regardless you already have notes. and then you can move notes in that view. 
So this feature won't affect you if you don't need it, and you can use it selectively.
Differences compared to a note with internal links:

• it's always at the navigation panel
• you can use drag and drop
• a note in single hierarchical view can have only one parent and you can't accidentally duplicate references
• it has an ability to create or remove notes right from the view.

I would definitely buy a Premium if Evernote had a good hierarchical structure view.