Mr. GROWF

For me (Mac user) the ability to EASILY (1) edit BOTH the Creation Date and Updated Date (2). I am scanning very old documents (1940s~1960s) that I want sorted automatically by date. (1) the Date editing is HORRIBLE requiring mouse clicks rather than typing in the date. This is INEXCUSAbLE in this day and age. (2) there is no ability to adjust the Updated Date and that is the default criteria on folders.

THANK YOU!!!!!!!!!!!!!!!!!!!!!!!

@Dave-in-Decatur my Use Case is simple. I'm archiving historical documents and I want the Creation Date to be the actual date the document was created. In my case that includes 1940s through 1980s. This is way the date entry is so impactful, whereas with Legacy I can simply type the Date (Ex: 07/04/1945). This date entry mechanism has the benefit of accepting navigational tabs so I'm not pulling the hands off the keyboard to click-for-a-date.

The ability to edit Update Dates and the cumbersome Creation Date editing interface is the sole reason I continue to use Legacy. For a document system it is baffling why this hasn't been replicated from Legacy. THE UI IS HORRIBLE FOR DATE ENTRY!!!!! How many clicks to enter a Creation Date of July 4, 1955? How about if you have 50 documents from 1955? ANSWER: More clicks than a human finger and sane person's patience can endure. I am archiving, cataloging, and studying documents from the 1940s through 1980s and the ability to enter a Creation Date and adjust the Update Date important. Before someone suggests - it is ridiculous to use TAGs or other work-arounds for document dates in a Document Management solution. PLEASE PLEASE PLEASE fix the Creation Date entry mechanism and allow physical typing of the dates (7/4/1955 or 07/04/1955 or 1955/07/04 I don't care). Requiring mouse clicks is horrible.

Many of us want to continue to use Legacy as the current version lacks features of the old client. I'm my case I want the ability to set both the Create Date and the Updated Date on articles. I'm going back and scanning old documents from the 60s, 70s, and 80s and want them in chronological order. The new EN client only lets you adjust Created Date. Even worse it forces the use of a Calendar date entry. So if you want to go back to January 1970 you are ENDLESSLY clicking on a tiny arrow (12 times for each year you go back!!). It is a horrible step back in user experience.

I do not mean to suggest the Plug-in is from EN, rather that EN Legacy is expecting a plugin which it does not find. Knowing what it is looking for will help us find that plug-in elsewhere, install it, and restore the display capability to EN Legacy.

@PinkElephant I have used a Legacy instance for many years. This issue is not present. I recently loaded the Legacy instance on a new MackBook and I get the "Missing Plug-in". This tells me the plugin can be loaded, but isn't by default. Because I have two different Mac computers on the same OS release with different experiences tells us we can find and "install" the missing plugin and restore performance on Legacy. Can you tell us exactly what plugin is missing? It is the Legacy application presenting that message. Everywhere else on the Mac PDFs are displaying fine. This is a "fixable" if we are told what Legacy is complaining it missing. Thank you

Be careful not to read too much into the lack of response for the bulk of users. The 80/20 rule would suggest 80% are using only 20% of the feature and via versa. Additionally, they likely think “it is what it is” even though they experience much much better date input everywhere else. Let’s be honest - most web and software interfaces allow BOTH manual text entry (preferred) AND mouse drive interface. That is what EN should do - don’t eliminate the mouse interface rather add plain text entry. Basic human interface design stressed minimizing moving hands off the keyboard to use a mouse (or other device) for mandatory input. So an interface that allows TAB navigation and text input is more productive, consistent, and pleasing.

I echo @Sandy Lemoine observations about date entry/editing. The interface is HORRIBLE when you need to select a date outside the current month. Super ugly when the date is over 8 years old. Similar to Sandy, I am collecting, scanning, and categorizing very old documents. I simply can not do it with the current Create Date entry mechanism. Sandy - I highly recommend reverting to EN Legacy where you can simply Shift+Command+i (at least on a Mac) to open the Note Details and BOTH the Create Date and Updated Date can be entered as plain text. For example enter "10/25/1908" will automatically resolve to "October 25, 1908 at 9:00 AM". You can switch seamlessly between current version and Legacy sharing a common database of notes. Until the current version of EN allows for equally efficient date entry I will remain solely on Legacy.

Thank you for the link. I will review Filterize and determine if I can leverage it to accomplish my requirements.

This version of the topic has a few interested parties, but there are other related topics with additional requesters. Still the number of users is small. 😞 The Creation Date should be the date the document was created NOT the date it was loaded in Evernote. Example: I cataloging documents from my grandfather originally created in 1930s~1980s. The “correct date” is when they were physically created not 2020s when I get them scanned into EN. It is very easy to adjust the date in Legacy version (Cmd i or Cmd Shift i - I forget because it is habit). I guess if it was never an option I would have adopted and alternate method, but it was and I did. I disagree with using Tags; 1) because the software has natively the date field just removed the ability to edit it, 2) each document has a different create date - would intend up with thousands of date-specific tags? I have not interest is Tagging to a year and everything being out-of-order in that year. 3) Using a Title or Tag requires special sorting vs the default. While possible, now I’m working around a different standard system behavior. I could use the last Updated Date, however it automatically updates when touched so when I’m adding notes, names of people in photographs, etc. I’d have to remember to reset the Updated Date and remember the documents original date. So I will remain on Legacy until either EN REenables editing Creation Date, I learn an acceptable alternative, or I move my content elsewhere. *** Post entered from a mobile phone prone to typos, abbreviations, and substitutions. ***

We shouldn't have to "work around" the ability to edit the UPDATED date field. As users we choose how to manage the dates field for our items. I appreciate the, "You shouldn't use it that way" and "There is a better way", but this should be the users decision.Z The fact that CREATE is editable is evidence that EN has the ability to make the UPDATED field editable. The reason(s) not to restore the ability to edit UPDATED is; 1) there is philosophical opposition to allowing that field to be edited, 2) prioritizing the backlog of requested enhancements, 3) A new (to the current version vs the Legacy version) foundational reliance on the UPDATE date not changing. I can't think of another reason why that capability hasn't been brought forward to the new releases. I desperately hope it is #2 because then we have a chance of getting that capability back. I can't move off Legacy until I have that in the new software.

I am curious if EN is even entertaining the ability to edit UPDATED date field? As to the suggestion in other threads to use another field or tags to replace our use of the CREATE and UPDATE date fields - Don't use date fields for dates?! I could begrudgingly accept this suggestion if there were extra date fields that could be repurposed AND we could tell the entire EN user interface to stop sorting by those system date fields and use these other date fields. To add insult to injury the mouse-click interface is horrible user experience for the reasons already stated - having to take your hands off the keyboard to hunt-n-peck with a mouse is contrary to efficiency and pleasant UX. It is not like users change the date by a couple days. Like many others, I load volumes of historical documents that I want dated to their original creation often decades ago. I ask EN's position because I suspect they have a visceral opposition to allowing us to edit the CREATE date. That they are absolutely opposed to allowing users to self define how they populate those fields. Unfortunately for me this is a absolute requirement. I won't be upgrading for the Legacy version until I'm able to edit the UPDATED date field.

I echo @Danny Bloemendaal's sentiment. As a document management system the #1 capability is the ability to apply a date to a document. Entering a date from 1987 is a horrendously tedious task with the new interface. Please reintroduce the plain text date entry. Secondly, we need the ability to set BOTH the Creation Date and Last Updated date. Again, I scan & metadata a mountain of older documents. That has become impossible with the new version. I will remain on Legacy until I can enter both dates.