In that there is a tag 'projects' and then nested tags for each client. In fact - in managing projects and clients my tags page looks something a little like a hierarchical filing cabinet (thought not quite). Both notebooks and tags would seem to be - when it comes down to it - a kind of meta-data/filtering device. Not being very tech-savvy about these things I don't really understand why unlimited tags with unlimited nesting are not a problem but notebooks are. We'll see if the notebook limit gets increased or removed (well, it will not likely ever be removed, but raised to some impossibly high number), it would be a good move, when it isn't at the expense of performance! I'm personally fond of flat and non-mutually-exclusive, but I understand how people might prefer something deep and mutually exclusive. That being said both schemes, flat and hierarchical, have their merits, neither one is more natural than another (though one is clearly much more prevalent than the other), and they have their disadvantages and advantages. No need for some specialized application. If I wanted hierarchy, I could probably just use folders in my OS to house plain-text files and website archives, all nicely indexed by my OS. At the very least I agree because almost every other thing out there is hierarchically structured. Evernote seems to think that the flat method is perfectly acceptable. This can give a really heavy user some extra time before hitting that limit (upgrading to business could offer a bit more relief, but that's not a perfect solution because it has its own limits).Īs for "should" Evernote offer hierarchy, this is a hotly debated topic in this community, and is ultimately a matter of opinion. Indeed, as you point out, once you get into the flow of the flat organizational scheme, the limit becomes a bit less of an imposition. CAN they remove it? Perhaps not until there are some significant moves made to ensure that performance is not seriously degraded.
Likewise, they could maintain the limit and offer a hierarchy.Īs for "should" Evernote remove the notebook limit, sure, I think so. Evernote could lift the limit and allow (theoretically) infinite notebooks, and still not offer a deeper hierarchy. Then there is the limited "hierarchy", or the choice to go "flat" (Evernote) rather than "deep" (filing cabinet, Window's Exploere, OS X Finder). Even with the 250 limit in place this seems to occur. The limit, I suspect, is in place partly to prevent serious performance issues if a database gets really large with lots of notebooks. There is the notebook limit, which has nothing to do with the filing cabinet metaphor. But there are really two things going on here. But now i've got used to it I believe it actually is as effective - if not much more so than the filing cabinet approach.ĭifferent strokes really, I suppose. I don't really know why Evernote have 'forced' people towards this rather than creating as many notebooks as they want. Its a somewhat different way of thinking from traditional 'filing cabinet' method.
In the tags section you can also organise the client name tags so they are nested under the main tag 'client'. Then add a tag with the client name to each note you generate. You just need a notebook for 'clients' - or a stack with notebooks divided into types of clients maybe. But then i tried it and got used to it and i can see it works very well. The idea of using tags didn't appeal to me. When I first heard of this I was also put off.
0 kommentar(er)
