How to Name Your Files (Easy 3-Step Formula) 📁 

Very good! Personally I prefer the order of date_code_description, or code_date_description, depending on the preferred default order of precedence for your file listings..

Good stuff! I was only doing date and subject but this adds so much more utility

Excellent advice good sir!

I only doing subject then date. Or date then subject. But this is really good

A great system. For books and published articles, I use: [author surname]_[publication year]_title, or summary of title_[edition number for books, if needed]/[journal abbreviation]. For other items, [identifying name] (because that is what I'd search for)_[date as YYMMDD]_[code: draft/final/issued, or Ltr for letter, Nb for note, Ref for reference, etc.]

excellent naming, and if there was a functionality to add the date and code automatically our work would be even easier and more productive.

You are touching a very interesting subject for me, so first, Thank You (thumb up). I am coming from code writing , dealing with not only file/folder naming, but also function and variable naming. the: date-subject-code seem like a very good way for orgenizing large lists of files. It's maybe of topic, How do you feel about folder names cmposed of "object-maintainer-name__object-name"? The maintainer name is a "role-type" like: gardener, flipper, translator, ... It give you a better stance from which to address the object. I feel ,in general, the need to avoid perminantly holding long lists! rather, have the search app: translate a search over object trees into a long temporary list to analyze, or as a summary to a question about the data. Just as the leading intention in this video is to help find a file in a list that is most suited to your daily needs, When I'm writing code the idea is to be able to visit an object folder and clearly understand the contents without knowing about neighboring folders. And, for code, Clearly understand separation between "roles" and "objects", The code should be readable to ppl as an instruction manual for them to do the job (or as recorded action log of someone who did it before), treating the processor as a helping hand. also: - I'm trying to limit folder content to "howto.c" and "obj.txt" - I'm naming functions to the form of: "doing_x_to(y)" or (example: var Iam = orgenizer Iam.fetching_Y_book_from(shelf_X) ) what do think?

I've recently started going through my files and renaming them. I've been filling out some of the boxes within the file properties to help out. Such as subject, genre, artist, contributing artist, year, ECT. Most of the files can also have a comment places within the properties section, for example photos of family events, I can add in who all is in the picture. You can also add in all those things within the folder the items are in, so you can sort through the various things mentioned above with only one click. I could sort by genre, subject, artist, ECT. It's time consuming, but is helping a lot. If only I had done it decades ago!

Ooohhh. The Version # is just what I need to add! I’ve pretty much doing name, Subject, and Date but the version number will come in very handy!

I don't take any chances, I use a three digit version number. Sometimes I use the hundreds digit to indicate a "generation" number for when I make major changes to a document, particularly my PowerPoint decks.

Thanks for sharing

I have no system and lotsa files. 😢