(See specific suggestions at the bottom of this message.)
I get how the tag approach works. It's not my preference, but I get it. The problems are that organizing with tags in the mobile or web apps is not up to speed. It's kind of dicey even in the desktop app.
This problem with tags in general comes out most clearly when using your existing tags (shown nested below in Tag VIew from a post in
For example for the set of nested tags shown in the screenshot above, when selecting a tag to apply to a note you would see ".NB.Business" and ".NB.NetSuite" as discrete tags at the same level, one near the top of the alpha list and the other much further down. There's no way to tell whether they are nested under other tags or each other or are at the same level. Worse, without scanning the entire list there's no way to know there's already the tag you need nested for example under ".NB.Business" or if it's somewhere else or if it doesn't even exist yet. ".NB.YB" would be way down the list and it's not clear if it's nested under another tag. Unless you have your list memorized it's chaotic and is certainly not amenable to staying organized when selecting tags if you don't use the structure/list every day.
"Flat" is the perfect word for it. If I'm filing using tags I haven't used in a couple of years, there's also no visual cue of where to look, made worse if the list is long. It's the old "where did I put it?" problem but compounded by the fact that you don't see the hierarchy when you file a note, so you don't get guidance of where you should put it when you file the note.
Sure there are endless sub-workarounds that might involve typing a complete nested structure into the name of every nested tag but now you're getting ridiculous. Isn't that what computers are for?
If there are suggestions in this post, they are:
Fix apps so they work properly to choose tags easily and efficiently
An ability to create "parent tags" so that EN starts a title for tags nested under it so the nested tab name reflects the name of the parent tag. This is so they sort together in tag selction lists, without having to type the structure into the name
Fix apps to show tag nesting structure when selecting a tag to apply to a note
Idea
suobs 6
(See specific suggestions at the bottom of this message.)
I get how the tag approach works. It's not my preference, but I get it. The problems are that organizing with tags in the mobile or web apps is not up to speed. It's kind of dicey even in the desktop app.
This problem with tags in general comes out most clearly when using your existing tags (shown nested below in Tag VIew from a post in
For example for the set of nested tags shown in the screenshot above, when selecting a tag to apply to a note you would see ".NB.Business" and ".NB.NetSuite" as discrete tags at the same level, one near the top of the alpha list and the other much further down. There's no way to tell whether they are nested under other tags or each other or are at the same level. Worse, without scanning the entire list there's no way to know there's already the tag you need nested for example under ".NB.Business" or if it's somewhere else or if it doesn't even exist yet. ".NB.YB" would be way down the list and it's not clear if it's nested under another tag. Unless you have your list memorized it's chaotic and is certainly not amenable to staying organized when selecting tags if you don't use the structure/list every day.
"Flat" is the perfect word for it. If I'm filing using tags I haven't used in a couple of years, there's also no visual cue of where to look, made worse if the list is long. It's the old "where did I put it?" problem but compounded by the fact that you don't see the hierarchy when you file a note, so you don't get guidance of where you should put it when you file the note.
Sure there are endless sub-workarounds that might involve typing a complete nested structure into the name of every nested tag but now you're getting ridiculous. Isn't that what computers are for?
If there are suggestions in this post, they are:
Link to comment
11 replies to this idea
Recommended Posts
Archived
This topic is now archived and is closed to further replies.