Jump to content


Level 1
  • Posts

  • Joined

  • Last visited

About Patrix47

Patrix47's Achievements



  1. Thank you for the idea. The Modified date is the key important handle on some notes as we have items that are supposed to updated based on specific periods. Notes like "January Sales Data" and "Last Year Results" should not show up as modified in July. They should be locked so they can be trusted as long as they are posted and remain relevant. Imagine reading a blog, news story, or email where every time you clicked on the words to highlight or copy an important piece the story "updates" itself. No two people reading the piece would ever be certain they are looking at the same data. In general though, the date handle is secondary. The bigger issue is that simply clicking to copy data in a note (on iOS) causes the actual data to change and be resynced. A mobile devices don't always have good connections and multiple people are often getting shared data at the same time this is VERY frequently leading to "Conflicts" (multiple versions of the same note) being spawned for no valid reasons. In a modern app, there is no reason a read-only view of data is not the norm. With Evernote, we have a case where auto-edit-only-mode is the ONLY way to actively access data. As an active note taking tool, I get the idea of auto-edit-only-mode. That's a big part of things like twitter and such as they always writing content in a forward-the-conversation sort of way. But even they let you copy a previous tweet and retweet it without destroying or changing the original tweet. Not the case with Evernote.
  2. We are still waiting for some response on this. The need continues and is a reason we have had to move some of our teams to other software. On Mobile devices, simply clicking on messages to copy text out of them is changing the date of notes and leading to data corruptions. Without locking, Evernote is not useful for frequently used reference information as it only works for frequently changed information. ...pat
  3. Just a followup to the Powers That Be: please do consider this idea: Note-Locking. As we enter the new year, I help run a number of business oriented Evernote subscriptions and the inability to lock notes (make them read only) once they have been put out there for the team or for a person's own account is truly an issue. The functionality is not far off form the idea of setting the share-accessibility of a note to read-only. The difference being is that you can set it yourself that way and reset the not to read/write if necessary for updates. Over the past year we can not count the number of notes that have been corrupted because multiple devices hit the notes at relatively the same time. the worst is with our IOS devices as your IOS-app changes the note if we simply look at it and try to copy ANYTHING (thus requiring an update/sync). We are not reliably able to use notes as reference because people are now afraid they are gonna cause sync errors (some notes have had dozens of these "conflicting change" notes strung to the bottom, which must all be resolved and cleaned up). If you are updating notes all the time, then the current Evernote setup is perfect, but if you setup notes to be reference or source info (to be copied from, not to) then the current Evernote is a serious FAIL and should be addressed. PLEASE do consider this. ...pat
  4. I hope that the good folks at Evernote are keeping an eye on this issue. We might not be generating some of the traffic of other bugs, but this request is substantial and greatly affects the capabilities of Evernote as a tool. Lock notes would allow for a significant number of features, uses, and techniques not currently available.
  5. +1 for the locking feature. Being that it is the beginning of the year, let me expand this idea and make the following suggestion/case for its use: A the beginning of a year (or other period) it is common to want to "lock" the notes from the previous year (period) and start with either a fresh set or continue from the existing but in a new note/notebook. This allows us to track progress and evolution rather than the current format of Evernote which only allows to relate the current state. Now I have gone through several forum posts on this topic as well as the obviously related "Duplicate a Notebook" and seen the engineering and design concerns and I would suggest there a couple of simple things that could make this work. First, there does not need to be an issue with raising havoc in terms of database search returns because the resultant notes/notebooks are inherently different. This difference can be manifest in several ways: - First, inherently the "second" notebook has a different internal ID and this could be leveraged in the search routines. - Second, when duplicating notebooks there "should" be an option to "lock" the previous notebooks or set their "status" to "archive" (or something similar). This would help all of us who want to lock/archive notebooks/notes based on real-world criteria so that we can work with Evernote's very efficient "current state" presentation method, and yet have the ability to "dig deep" to find something we may have left in the virtual "way back machine". - Another way this can be accomplished is through the use of tags. This is something both Evernote could do internally and us users could do on our own. For Evernote, they could allow a set of tags to be automatically applied to Notes/Notebooks upon creation (such as a "lock" or "archive" tag), then when searching, they simply have to allow us to be able to automatically include those tags as part of the search. The action and presentation of this is similar to the way OSX Spotlight currently searches with a keyword/search term and allows the user to specify if it is "contained in" or "part of the name", etc. If the user opts that all searches by default would be on "current items" then they would then have the option to click on their search term and specify that the query should be across all notes, not just their default filter. There are additional benefits to this process as I have recently helped a business begin to use Evernote for multiple employees who all share some common notebooks. Now one of our biggest problems so far has been the inability to separate personal and professional data. If you are allowed to see one of the group notebooks, then those results ALWAYS show whenever you search for personal items. And, unfortunately, and VERY VERY VERY embarrassingly, the reverse is also true. As a result employees are currently instructed to only use their Evernote account for business use because of several instances where personal information "popped up" when users searched through notes during meetings. Now I can tell you this has been a deal breaker for using Evernote in more than 3 other large deploys. Of course, it is possible to search within a single notebook, but obviously this is not adequate when businesses make use of multiple Notebooks for activities. So far, we have tried to apply tags to our notebooks so those that do use Evernote can search all of their business notes by referring to a single tag for all Business Notebooks/Notes. However, most of the time users don't enter tag data in before they enter search terms (this is normal: search for what you want then refine the scope). This still result in embarrassing returns, but can be quickly modified by adding the tag to the search. The simplest answer would be to allow users to define a profile (or multiple profiles for advanced users) for their standard search/search patterns. This way, be default they can search in only a "current-business" world, or in a "current-personal" world, or an "archived notes" world, or maybe just "search everywhere". But the user is in charge, not the UI and they get the results they want immediately, not after fighting with extraneous returns produced by the instantaneous nature of the search engine. Evernote is powerful in the way that it allows us to capture the details of our world in a clear and useful manner. What I am suggesting is that the same level of design effort be applied to the returns of data that Evernote presents to users – as a blunt search return can deliver not only too much data, but can actually produce embarrassingly "wrong" (for the user-situation, not for the search-engine) data.
  • Create New...