Jump to content


Level 2
  • Content Count

  • Joined

  • Last visited

  • Days Won


Karetep last won the day on February 9 2014

Karetep had the most liked content!

Community Reputation

9 Neutral

About Karetep

  1. Hello nc40- Yes, love your contribution here. The TEAM TAXONOMY ENGINE is way-cool and definitely is another strong usage scenario where EN could blaze the path!! Your other two points are also rock-solid, I'm Loving It!!
  2. One additional point. There is another reason why the nested tag functionality that is being proposed in this thread is so important. It allows folks to develop their own semantic taxonomy standardization in a very quick and simple way. Without going too deep let me briefly explain: Lets say that I'm a project manager at a large company. Lets say I have developed my own personal way of categorizing projects. However incorporated into the 'semantics' of my categorization are my own personal 'standards' for how to handle things like project lifecycles and the time dimension. Here would be an example tag tree: (wild example - not much thought) Project A Governance Phase Steering committee New Fiscal Investment proposal Prep Review Final This hierarchy would mean certain things to me. So for example if I want to look at all Steering Committee actions across all Projects that have new Fiscal Investment proposals that are at least in the Prep phase I would click on Steering Committee - the dialogue box would pop up and I would type in -2. EN would then return all notes with the Steering Committee, New Fiscal Investment proposal and Prep tags. Or, let's say that I wanted to give a new project only the following tags; Governance Phase, Steering Committee, New Fiscal Investment - then I would drag the new note to Governance Phase and type -2 in the dialogue box. These are very simple, straight-forward actions but it allows me (and others) to manage the semantics of their own personal taxonomies. I personally believe that this is a very very important part of content management. Because as our lives become more and more digital - the only thing that will separate organized folks from unorganized ones is the level of detail with which they develop their personal semantic taxonomies and the rigor with by which they apply them. Another way to think about it is the following; your personal semantics and taxonomy becomes equivalent to the Cloud but instead of a Cloud for content it is a Cloud for your idea-organization-system. The ability to create these then frees you from being locked into any one tool because once you develop the taxonomy you can implement it in almost any tool. However, the tool where you create, manipulate and store the taxonomy will end up becoming core to your life - THIS IS EXACTLY WHERE EN WANTS TO BE - IT WANTS TO BE CORE TO OUR LIVES. And this is why expanded tag functionality has a lot more value underneath the covers than might be initially apparent. BLAZE THE PATH EN - BECOME OUR PERSONAL TAXONOMY ENGINES.
  3. Yes, correct, my description could have been clearer. In my proposal you would only drag notes to the tag tree if in fact you wanted to add tags to the note. If you don't want to add tags then simply clicking anywhere in the tag tree would pop-up the same dialogue box where you could enter things like +3, -3, etc. (e.g. +3 would mean all tags up to three levels above the current tag and -3 would mean all tags up to three levels below the current tags) and EN would only display notes with those tags. Actually, this is a great UI design- because it frees the user from needing to do queries when they have something quick and simple that they want to do. Remember my philosophical point - we should give folks plenty of ways to do stuff. This would certainly not complicate the UI but in fact make it simpler and more usable. Also keep in mind that you have also agreed that you are for expanding the functionality of EN - my proposal would certainly expand the functionality of the sub/super tree UI but in a very simple and intuitive way. There is nothing in my proposal that complicates the UI. Let's see: 1) Folks are already dragging notes to the sub/super tree UI so no changes there. 2) Folks are already very familiar and adept with friendly easy dialogue boxes so no complications there. Hmmm, I guess I fail to see the complications that you are referring to - on the contrary I only see enhanced functionality provided in a very consumable, easy and user friendly fashion. Regarding your other points about labels in Gmail - I think we're basically on the same page and essentially saying the same thing. We both agree that there could be more functionality to both Gmail labels and EN tags. Where we disagree is that you are still not certain that expanded functionality (for tags) is necessary whereas I definitely feel that it is both necessary (more ways to skin the cat) and that it would be a huge market win for EN.
  4. There is an over-arching philosophical point in this thread that could be getting lost. ONE SIZE DOES NOT FIT ALL. I like many of the approaches and themes laid out in this thread. The point is - we are all different and even if were all the same - we all have the need for a different 'tool' for different jobs in our busy lives at varying points in time. There may be cases where we only want to look at the notes with tags in a tag tree. There may be times we want a simple way to add the tags in a tag tree to a note. There may be times we only want to add specified portions of the tag tree to a note. The point is - we need this variety of capability available to us. It's really very simple. Think about a spreadsheet. Spread sheets used to just do simple math. But as we all know we now can not only do simple math but statistics, trigonometry, advanced financial calculations and so forth. We sometimes tend to limit ourselves by thinking that one person is advocating ONLY for a particular solution, when in reality we need a broad selection of capabilities available to us. Nested tags (with all of the functions described above) is one such very important tool-suite that we need in our tool-kit.
  5. The way you would do this is as follows: Lets say you had a tag tree that had 10 levels L1 - L10. Let's say you want to tag a new piece of content with only the last 3 levels. The feature would allow you to drag your note to the tag tree and then provide a pop-up box (or part of the search syntax) that would allow you to specify up or down and a number for the number of levels. So for example - to execute the first example that I mentioned - I would drag the new note to L8 tag in the tree and then type "down3" (or perhaps -3) in the pop-up box. The feature would then populate my new note with the tags for L8 - L10. If all I wanted to do was see all notes with the L8 - L10 tags - I would just type 0 in the pop-up box and the feature would then only display notes with tags L8 - L10. Not necessarily. I have always considered Gmail labels to be somewhat underpowered. Yes, they are definitely a step forward for email but they're almost like a tease - in the sense that they tend to leave you wanting more functionality. For example, wouldn't it be great to have nested labels in Gmail??? And wouldn't it be great if the nested labels worked the way we are describing them in this thread where new mails could 'inherent' specified parts of the "label tree"??? So bottom-line, mediocre is still mediocre no matter who has done it. Just because Google has thus far only taken labels to a mediocre level doesn't all of a sudden turn a mediocre implementation into excellent. Remember- the point of my post was to encourage EN to take the LEAD.
  6. I agree with Tomass that we need an improved approach to Nesting. I also tend to agree with Jefito that we should keep Notebooks and Tags separate. What Tomass is describing is essentially a Nested Tag solution which I believe EN could benefit immensely from. See my reply on: Feature request: Autotag notes with tag hierarchy of nested tags http://discussion.evernote.com/topic/37385-feature-request-autotag-notes-with-tag-hierarchy-of-nested-tags/
  7. Hello- Long time EN user here. It's time for EN to step up and provide some actual functionality for the Nested Tags. As we know, today it is just a visual hierarchy with no underlying semantic relationships of the items in the "tree". I definitely see a need for both bconrey's and gustavigi's approaches. I have one modification to add. The ability to select how many levels 'up' or 'down' the tree you want to add to the new note. This would simultaneously address both requirements. I am not a big fan of jefito's approach for several reasons: a primary objective of both bconrey's and gustavigi's proposals (and mines) is to actually add the tags that you want to a note. Jefito's approach would not add the tags. the approach would return all notes that had the 'subtags' in the tree in question whereas I may only want portions of the tree (this is very similar to the concern that gustavigi expressed) I'm neither unrealistic or greedy and would be very happy with a phased approach from EN. Maybe start with gustatvigi's suggestion of adding bconrey's suggested functionality but also keep the current functionality. Then in a subsequent version add the feature I am proposing of being able to specify how many levels 'up' or 'down' you want to include. Either way- its time for EN step up it's game regarding nested tags. Thousands of us need greater functionality from tags. The Taggify solution for Mac is a great proof point for this. Here's the real deal for EN (or value proposition if you want to keep if more formal) Those of us that are advanced users of EN know that the next big thing about to explode on the scene are "one-stop" solutions for content management and task management (email, social (Facebook, Twitter, etc.) , blogs, rss, etc. Contenders like IQTELL, and Unified Inbox are coming on fast. EN is still the overall best 'one-stop' but must continue to innovate to stay ahead. It is my opinion that adding more functionality for tags would be one of those "Kano" 'nice-to-have' features that would put EN solidly in the lead for a long time to come. As we all know 'nice-to-have' features eventually become 'must-haves' so EN could really solidify its lead by being first out of the gate with advanced Tagging. Eventually one of the "one-stop" contenders will search deeply for EN weaknesses and discover this one about its mediocre tagging solution and exploit that weakness to gain market share (that's the way market disruptions work folks). So IMO, beefing up Tagging is a solid, no-brainer, win-win proposition for EN.
  • Create New...