Jump to content

vertium

Level 1
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

3 Neutral

About vertium

Recent Profile Visitors

312 profile views
  1. Exactly. To have people say "well, that's the problem with the way you set it up" is ridiculous. EN is one of the most poorly documented software products and to respond with it being the user's fault is insane. Between there being no "best practices" (with all the implications, pro and con for the choices you make) being published by Evernote, and leaving it to community support makes me wonder why I bother. At least with Adobe forums, you have people with 15-20 years of using the products giving advice. Here, everyone's an expert with how they set it up or how they think it should be, with little experience or expertise in how it should be setup or optimized. I'm about done with it altogether.
  2. Then you've figured out something that has eluded me. Sure, you can export to HTML, but when you do, you've got at least 2 assets to manage for each note you export: The HTML file and then the actual attachments in the notes. And now you have to keep both of those resulting files on your file server forever. Because the HTML is nothing more than a link to the attachments, a note that has multiple attachments and a ton of text, tables, etc. is not easily "managed" once you export it. And if you want to use the XML export, when you import into another tool (e.g. Apple Notes), all markup/markdown information is lost. Can't speak to OneNote as I don't buy anything from MSFT unless there's no other viable choice. Let's just call this an "inelegant" approach and leave it at that. It's not a criticism that EN is trying to lock you into keeping your notes with them forever, I understand why'd they do that. But there's always a point where the effort needed to "simplify" becomes too great, and the additional capabilities provided (e.g. OCR search) aren't enough to justify a subscription fee that can only be expected to rise again in the future. EN's not expensive per se, but from my perspective locking in your customers and then raising the price is never a good combination for customer satisfaction. I really do appreciate the comments and insights, from you and others. If find this forum helpful, but very similar to those "community-based" support approaches used by Adobe and others. In lieu of spending EN money on actually building best-practice guidelines and extensive tutorials on how to get the best value from the service you're buying, they rely upon volunteers such as yourselves to do their support work for them. And no offense intended, but telling me that it's "easy" to do something or sharing how you've used it doesn't necessarily fit the bill of a "best practice". The software was presumably engineered. That means an engineer should be able to tell a product marketing professional how it is intended to be used, how to use it most effectively, why that decision was made, how to communicate that to the user base and then the product marketing team should build the necessary learning assets so the user community can learn about all the wonderfulness of the engineering effort. I've worked in the software industry for 30+ years. I fully understand how it's supposed to work. But EN has shirked its responsibilities and shifted all the burden to the user community itself, which despite having great input, fails in the first few steps of the design and engineering process outlined above. EN expects me to sell myself on why I'd want to continue using their product, or equally bad, expects those who answer questions here to do the same. I'm paying THEM the money, I'd like them to sell me on it. At this point, I'm on a quest for a completely different approach. To me, it's silly to have to do so, but until I get this figured out, I'm going to have my staff export all the attachments from EN and reinstitute a file structure so I can have the source documents at my fingertips if needed (I guess it's a good thing we have 90+ TB of storage on our network). Moving forward, I'm going to never discard any attachments I put in EN. I'm going to burn double the disk space needed simply to have search inside my PDFs. As you might imagine, that's not a good feeling on my part, but I can't go forward throwing stuff into EN given the chance that I won't be on this platform when my subscription comes up again for renewal. I've reached the point where the work necessary to use this has outweighed the benefit it provides.
  3. I do agree, computers are not naturally intuitive, which is why UX designers get paid very well to make an application work the way people tend to think. Further, I completely agree with the notion that the software team can build what they think is best, and the marketplace will vote with its wallet, though your notion that a business should just do what it wants at the expense of attracting the most users, is simply not the way businesses work. However, now that we have those fundamentals out of the way, I'm desperately trying to figure out how to make EN work for me in a way that allows me to leverage it's good capabilities. I'm not just sitting here griping that it's not hierarchical, I'm saying that its design is too hard to work with and trying to learn a better way to use it. I have thousands of notes, that I can't effectively use and it will take me hundreds of hours to move them all to another platform (EN made sure it was VERY difficult to get stuff out of it... which if I'd researched better would have been a disqualifier when I started using it in 2010). I don't even know how to respond to the tool/religion remark, so I'll just leave it at that.
  4. Fair enough, thanks for writing. Still doesn't work for me, so I have to consider alternatives. Right now, EN is the equivalent of a searchable junk drawer in my kitchen. It's all in there, but I won't find what I'm looking for unless I remember either the specific tag I stuck on it or happen to remember a fairly unique word that might have been in the document. With thousands of notes, it's fairly hopeless.
  5. I understand the issue, understand the message above any my only comment is that after using EN for years (since it first came out), it never gets used as often as I would like it to because it forces us to think the way that the EN design team thinks. This is bad software design, pure and simple. Software should be intuitive and while, as csihilling states, in his opinion tags are better, they're really not better if people can't easily and quickly learn how to use them to achieve their desired outcomes. I get that the gurus here are just that... people who've mastered EN and I thank them for their time and dedication to helping others. It really is appreciated. But, as is the case with most mass market software applications, the "help" in EN is ridiculously underwhelming and the user community far too often presumes a level of understanding on the part of the questioner that they aren't sufficiently explanatory in their response, leaving the questioner even more confused. In other words, if you want your user base to "think differently", in order to adopt a metaphor and structure that goes against the fundamental way people interact with documents and information in most other media (including, but not limited to their file systems, the physical world, etc.) then there really needs to be a more comprehensive, consistent learning path for new users and those longer-term, more experienced users who wish to leverage EN even more (which includes me). At this point, I keep EN primarily for it's OCR capability so I can find documents by a word search. I respect csihilling's preference for fewer notebooks and more tags. Only two things that I object to in it... 1) it's his preference, not mine (and I've yet to see a compelling, clear explanation for how or why to do it that way); and 2) it's not how I think. When going from my file system to EN to my bookshelf loaded with physical binders, it's just too difficult to have to switch off one way of thinking in lieu of another the dozens of times a day I'd have to if I didn't keep all my EN in the 200+ notebooks and stacks I have today.
  6. though fairly snarky to feel the need to point it out.
×
×
  • Create New...