Jump to content

karatedog

Level 1
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

1 Neutral

About karatedog

  1. If I understand properly, this would result in multiple levels of notebooks represented by tag hierarchy. Which leads back to my original question (which popped in my mind, reading a lot about the tagging system): If the tagging system is to be enhanced (and not the notebook hierarchy), why there is a one level depth at all?
  2. This is the proper sign of an underlying architectural problem. These "tags" are tied together on the wrong level, which results in tags like "project_documents" and "project_info" and you'll have "project" duplicated. Although the Search functionality is smart enough to find text fragments, that way searching for "projec" will work.
  3. You need to get to now Set theory deeper . If you want exactly 1 level of stacks and I want unlimited level of it, my "valid" way contains your "valid" way. If the software knew unlimited levels of stacks you could still use only 1 and we could both have our "valid" ways without clashing. Those "valid" ways would collide only if we wanted the same thing but with a different predefined property (you want 1 level, I want 2). And you are generalizing that the whole tool is wrong just because one of its - smaller - functionality is wrong. Evernote has problem, but for this one there are no work
  4. How can "having more depth in hierarchy" be more restictive than having 1? I understand your point and it works well for people who have so much information that they have to use search functionality all the time. They really need to categorize the data (tagging), that data can be anywhere, because its location just doesn't matter. These people wouldn't be harassed by even a totally flat note structure. However project managers like me (and around me) are cursed with some data organizing habit. So I keep my projects in folders (named by the project's name), and when I want to work with som
  5. You forgot to mention what you are working on. A CRM system? Maybe on the LHR? So even it is "enterprise" and "multi-billion dollar" it is not necessarily justifies not having a tree structure in information organizing. Facts: people usually use computers, and those computer organize information in file-systems, and it is logical. Therefore it is no wonder these people would like to use the same information organizing method they have been used to for ages. Why these people don't accept the logic behind the "we have only tags instead of notebook hierarchy"? Because Evernote has hierarchy, alth
×
×
  • Create New...