Jump to content
Updates to the Evernote Discussion Forums! Read more... ×

drewla

Member +
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

7 Neutral
  1. FWIW, I think it is appalling. Like many other software products that I've loved over a long period, Evernote seems to have embarked on the "going backwards" phase. They seem to devote a lot of time and energy to introducing features that no one appears to ask for, while getting wrong the really useful, simple stuff that users actually want. Depressing.
  2. I wonder if someone can help me please? I've been using EN successfully with my Mac and ScanSnap to scan and import a large number of paper documents. (I use Hazel to send to Evernote from my "Scanned Documents" folder.) I'm not sure how this has happened but a number of files have been re-sent to EN and are now duplicated notes. Others have yet to be sent to EN. It's got messy. I need to do an audit so that i can compare the files sent to EN with the contents of my scanned documents folder to check for both duplicates and files not yet sent. The easy answer (I thought) would be to sort the notes in EN according to the PDF filename, allowing me to rapidly spot duplicates and to compare with my folder contents. But I can't see how this is possible. Is it just me? I can't compare note titles with stored files because I've renamed most of them as they are imported to make them meaningful and indexable. Each note bears the filename and note title prominently when viewed, but is it impossible to see just a list of underlying attachments i.e. filenames? Failing that, does anyone know of a utility that would do this? Or otherwise have an idea how best to approach this problem? Any pointers would be greatly appreciated. Thank you in advance.
  3. Anyhow, hopefully the discussion in the thread I linked will be of assistance. I doubt it will stop the "interminable correspondence," and I don't think the discussion should stop. Bring it on! It's good for Evernote to hear customer voices. Thank you, there are some useful looking links there. I'll check out some earlier responses. As for a current solution, I've realised that my best best is to look at 3rd party tools (a couple mentioned in this thread look promising).
  4. Thanks -- yes, I'm aware of nested tags, and they are better than nothing, but not ideal.
  5. Yes, tags are great. I love tags. But it's not an either-or. People are not saying "tags are bad, let's have a deeper hierarchy instead". They are saying that the choice should be a fairly vital part of an efficient note and document organising application. Sometimes tags are absolutely the right tool to use --- and sometimes a tree structure is much neater and assists maintenance. Whenever it's pointed out here, yes, we get helpful workarounds (thank you everyone) -- usually forcing tags to replicate something akin to a tree structure -- but it's nearly always a second best. We don't want to constantly have to search for things. Frankly, I don't always know how best to search for something and will find it quicker if I can visually trace it in a hierarchical grouping. We do this all the time in a standard file hierarchy, when a search isn't always simple and neat. Heck, sometimes it's just useful to be able to survey what we have in our systems by doing a general visual overview. We can spot gaps and anomalies in a split second that way. And anyway, the fact is that Evernote already has the concept of notebook stacks, which is itself a hierarchical grouping structure -- albeit a shallow one. So the complaint is not that they should introduce a conceptually new feature, but should complete something they have started. By pointing out that the discussion has come up many times before illustrates how much pain it causes people. It really does reduce Evernote from being pretty much the perfect tool to being a really good tool with one very annoying flaw. i don't want to be told that if I don't like it I should go and use something else. That's a little dismissive. EN is so nearly everything I need, especially with its brilliant paperless / scanning features. I won't throw the baby out with the bathwater. As for: "*Answer: because they own the product, don't have to defend or comment on every decision they take, and (sensibly) do things that fit in with their long term plans, without getting distracted by requests for 'easy to implement' changes", ...that strikes me as arrogant and rude of EN. There is never an excuse to ignore your customers, especially when the same question is constantly raised. I use/have used many software forums and it's very common for the company to respond to a request that is constantly made. Even if it's to explain why it's not present (e.g. too difficult to implement or contrary to some underlying guiding principle), or that it's on some roadmap, would be respectful to their customers and be sensible customer-service. Perhaps best of all, it might stop some of these interminable correspondences.
  6. drewla

    Tabs within notebooks

    It's not that there is no method of classifying a complex hierarchy of information (like the railroad example) in Evernote. Sure, you can tag and multi-tag and multi-multi-tag as you want to create a structure. But there is a reason why the folder > sub-folder > file structure has endured so well. It replicates the way most of us like to store information. I love hierarchies. But here's the thing -- I love tags too. Sometimes tags are better, and just because I find nested folders a natural way of organising multiple related files, it doesn't mean I don't see the tremendous value of tags. Sometimes one is better, sometimes the other. What I love about Apple's Finder is that you have BOTH. I put nearly everything in a folder structure in Finder but sometimes I want to link stuff together in ways that prove impossible or inconvenient with folders alone. Tags are a perfect answer. So for me the value is in the choice, and the ability to deploy each where it works best. It's like having to choose between a knife, a fork and a spoon to eat all meals.It's pointless trying to argue that one of these implements will do everything well. We end up with one of those weird spoons with a sharp edge and three little prongs. Clever but much less effective than being able to pick up the correct tool for the job in hand. One final point -- the fact that EN has created the concept of a notebook stack seems to acknowledge that they see a value in visually grouping information in a hierarchy. Why else would they do it? Now if they would only allow us to deepen that stack beyond one level to multiple levels, we would have the best of both worlds.
  7. drewla

    Tabs within notebooks

    No, of course there isn't. It can be quite a positive and constructive thing.
  8. drewla

    Tabs within notebooks

    Some fair points. Rather than tetchily go through each one, I'd prefer to seek a note of agreement which I found in your final observation. I'm with you on this -- I think it's counter-productive to whine about functionality that doesn't exist, and we should use such situations to challenge our own preconceptions and prejudices. That said, it's good to prod developers with other perspectives from time to time. and it also prompts others to offer workarounds or alternative approaches.
  9. drewla

    Tabs within notebooks

    I'd like to add a couple of comments here. I've had an EN account for about 5 years but started using it a little more regularly last year, and have recently decided to get into it more seriously, now that I've embarked on a paperless crusade. Like a lot of ex-OneNote enthusiasts, I too miss the sub-pages and tabs hierarchy. I won't go as far as to say that EN "should" follow this model, but for me it made logical sense and keeps things neater. I know that in EN I can collect notebooks in a stack at a single level, and use tags to semi-replicate the tree structure if I wanted to. But it seems artificial, and doesn't work very well. The concept of tags is good but they can be annoying too -- not least of all because you constantly have to manage them. I tend to be on a permanent cycle of rationalising and eliminating unnecessary ones, then adding to them again when what I'm left with seems too general. What's worse is that tags are all or nothing. You either tag universally and rigorously or not bother. Anything else means you can't trust your lists to be accurate. There are other reasons why tags are not always the best answer. I may have a bunch of documents and related notes and I just want to physically keep all in the same place without having to individually tag everything. I may want to see them collected together in a rough and ready hierarchy, perhaps just temporarily. EN doesn't even have to think in terms of new concepts like "tabs" and "sub-pages". I'm well aware that isn't an original comment / request, but If we could stack notebooks more than one level, the problem would be largely solved. Keep all the same terminology and concepts but just allow users to nest notebooks inside other notebooks a few levels deep. Would it create serious technical issues? Hmm, I don't know, even though I am an ex-developer. I might have thought that as long as EN wasn't attaching additional functionality to the levels (e.g. altering the features / metadata, or the visibility in searches etc) then this could be a reasonably cosmetic change. So the lower level would appear to the user to be at a different level, to help with organisation, but to the EN logic engine, would still be regarded as just another notebook under the top level. That aside, I think Evernote has many excellent features that are not found in OneNote (etc) and this is why I've decided to go with it. Just finally, on this subject of rudeness etc, having scanned the forums quite a lot over the past couple of weeks, I do find some moderators and 'evangelists' can be a little bit obnoxious too, even if that doesn't manifest as overt name-calling. More a slightly supercilious attitude, and impatience / exasperation with those who are yet to cross the line into the full EN 'lifestyle' thing. I appreciate the time they put it, and am interested in their views on the software and best practices -- but not their sarcastic comments.
×