Nirvana 2: Tag Management
In general I really like the improvements relating to tags in N2. However I miss the ability to assign tags that aren't Areas, Contexts or Contacts. I like to filter some of my tasks by tags that don't fit in any of these categories but currently can't. If I try to create such a tag, its automatically turned into a context, which they're not. Since I want wo keep Areas, Contexts and Contacts as distinct categories, I suggest adding regular, "flexible" tags to the above types of tags.
Comments are currently closed for this discussion. You can start a new one.
2 Posted by Proximo on 22 Nov, 2010 06:44 PM
Several others have mentioned this issue as well.
If we had dedicated context and a dedicated contacts feature. We could use tags for labels as we see fit.
Maybe there is a way to designate what type of tag we are making. This way they are color coded and normal tags won't need to be associated with a context, contact or area.
hmmmmm
3 Posted by martin.tyler on 22 Nov, 2010 10:23 PM
i've not looked at it closely - but what is it about a context that makes it unsuitable for other uses?
i had a few other tags which now in N2 i guess must be contexts, but it all works the same - the ones i actually treat as contexts i named starting with an @, the others are just lower case words
4 Posted by Proximo on 22 Nov, 2010 10:43 PM
When you want to manage them, they show up under context and since Nirvana is based on GTD, this is technically not correct.
A context in GTD is a Resource or Location
A Tag is just something you use to label something with.
Just saying. :-)
5 Posted by martin.tyler on 22 Nov, 2010 10:49 PM
Aha, i'd not 'managed' them before
still, by prefixing actual contexts with @, managing contexts/tags in one is still pretty simple, and not something you have to do often
ideally they should be separate of course
6 Posted by Proximo on 22 Nov, 2010 10:51 PM
It's not a show stopper for me at all, but it is something I notice sometimes and just wish to have a dedicated context feature.
I don't use @ for any of my context but I still add some tags here and there. Like you said, it does work but if we wanted to do things in a GTD way, there should be a difference between tags and context. :-)
7 Posted by Rique on 23 Nov, 2010 02:53 AM
Proximo, I agree 100%. Tags are not contexts. Contexts are not tags. And a good reason to treat them separately would be to open up the possibility of managing them differently.
For instance, what if I wanted the tag filters in the top bar to be shown - or not - based upon what kind of tag it is? If tags and contexts were "the same", then I could not do that. So, even thought that functionality is not here today, it would be nice to treat them separately to allow for future flexibility in tags management.
"Under the hood", everything can be a tag - I don't care about that. But as far as the UI goes, there should be a delineation.
8 Posted by Proximo on 23 Nov, 2010 02:22 PM
@Rique
Very good point.
Not sure how you can distinguish between them if everything is a tag under the hood, but maybe this is possible.
David McLaughlin closed this discussion on 11 Feb, 2011 11:12 AM.