What's the Proper Way of Naming Files?

RadCazz · 23 Feb 2018

Over the years, I've come across dozens of ways to properly(?) name a file. For example, as in my movie, here are just a few:

The_Secret_of_NIMH_1982
The-Secret-of-NIMH-1982
The.Secret.of.NIMH.1982
The Secret of NIMH_(1982)

I think some of them may go back to the good ol' PC DOS days. Not sure.

I ask this because I'm going thru ALL my files and tediously re-naming them, for conformity's sake, but I want to know the universal/proper/accepted/etc. way if there is one!

Thanks!

lehnerus2000 · 23 Feb 2018

I don't think there is a "proper way" to name files.

CLIs often use spaces as delimiter characters.
When you use the Command Prompt, this is why you have to surround path names with quotes (if the path contains spaces).

Linux Distros used to often have dummy spits when they encountered spaces.
Old-School Linux users often use underscores and dots instead of spaces.

Web-based stuff can have problems handling spaces (a lot of web servers use Linux).

Some software automatically replaces spaces with a code.
This is why you can sometimes see filenames/URLs like "word%20word%20word".

PolarNettles · 23 Feb 2018

There's no universal standard - it's up to the individual or organization to come up with their own naming conventions (or not).

However, there are some things to keep in mind if you are sharing with other people using different OSes:

As lehnerus2000 said, spaces are annoying to handle in various situations so a lot of people use underscores or dots, although all OSes can handle them with proper escaping.
Windows has reserved filenames (like NUL, CON, PRN) that have special meaning on Windows but other OSes treat like normal files. So if someone using Linux creates a file called "nul" and sends it to you, Explorer can't open or delete it.
Windows won't allow filenames with certain characters that other OSes are fine with - Naming Files, Paths, and Namespaces (Windows) . I recall a thread on this forum where someone couldn't delete a file because it had a trailing space, which is allowed by Linux but not on Windows.
Unicode handling between OSes is tricky so sticking with ASCII is ideal
Maximum filename and path length is also different between OSes

margrave55 · 24 Feb 2018

For me there is only one rule. And that rule is "I do it anyway I feel like". Whatever makes sense to me becomes my method.

There is no universal "right way". Just do it "your way".

gpstoloff · 24 Feb 2018

One hint is that, if you're trying to store files in date order, include the date in YYYYMMDD or YYMMDD order.
Then, let File Explorer & ASCII sort it out automatically, every time you refresh the directory (F5).

Berton · 24 Feb 2018

Sometimes to keep files in order that have 1, 2, 3, 11, 22, etc., in their names it usually works good to 'pad' the number with zeros as in 01, 02, 03, etc., allows 11 to follow 10. My usage goes back to the early '90s and the DOS naming convention of 8.3, up to 8 characters for the name and up to 3 character for the extension most often assigned by the program creating the file. With the advent of Windows 95 came the introduction of LFN/Long File Names which does allow creativity but still the extension needs to be what a program recognizes to be able to open it. There are some restrictions by the Operating System in characters that can't be used but there's always a prompt about them when that is tried. Now with the use of large-capacity drives/more partitions possible and external drives there is also a limit of how long a name can be caused by the 'path' to where the files are stored.

lehnerus2000 · 24 Feb 2018

Berton said:

Sometimes to keep files in order that have 1, 2, 3, 11, 22, etc., in their names it usually works good to 'pad' the number with zeros as in 01, 02, 03, etc., allows 11 to follow 10.

I use that method for folders.

What's the Proper Way of Naming Files?-my-file-folder-conventions-01.png

gpstoloff said:

One hint is that, if you're trying to store files in date order, include the date in YYYYMMDD or YYMMDD order.
Then, let File Explorer & ASCII sort it out automatically, every time you refresh the directory (F5).

When I create Backup Images, I use that method for System Reports and Storage Setup.

What's the Proper Way of Naming Files?-my-file-folder-conventions-02.png

DonMurray · 02 Jan 2020

CATAGORY-revision-jobnumber-date-description 3digits 3 digits 4 digits date- than a longer description. branch(aaa-rev-x11x-date-mm-dd-textdscpt)date-mm-dd-descrpt.blendthen for parts for the filePartFOR)aaa-s01-x11x-date-mm-dd-textdscpt(date-mm-dd-descriptions

K11-rev-x11x-date-mm-dd-basebboardnotes.TXT

My thinking on this is that I will somewhat depend on date sorting but I will know when date sorting is wrong. When I put files up on a web server the server does not differentiation between the last 10? digits it just uses the same file. So I am putting the category first then version then date. That way I can keep my files sorted easily like I can put a z as the first letter and it will join together with all the zs. Folders: I make a template folder file that has all my groups of purchase orders and work orders to common vendors and contractors.
this works our great. I started using a file re-namer to put a job name at the end of each of those so I can link it to favorites. (below is a template of folders I renamed with snek at the end)

What's the Proper Way of Naming Files?-snek.jpg

so here is a template for folders that i renamed with snek on the end of each one so I can put a link in favorites and know what project it is when I click on it. I do the same thing at work but for the template folder for each job showing the vendors and contractors.
most of the time I name my files what ever and when it comes time to find files I do not know what is what and I do not know if the dates can be trusted. So like now I propose to use the first 3 characters so my file will be categorize by category first and then version. ----So now if only I stick to it. The one good thing about this is that if I get lazy I can always just put the first three characters in and blow off the rest. so I can put dum- if i cant make up mind but at least all my dum files will be together.
The biggest thing is consistency. people will argue to put the date first but I fear web servers and email attachments will get messed up 20181225-A will be treated the same by a server as 20181225-B as far as I know when I email files and attach files things get mixed up and the email server will just use 20181225-A when I sent the B so cat-rev-text-datemmdd seams to fit better. Most of the time the date sorting works - unless you copy the files the wrong way and then they will all have the same date. Plus some systems are backdated so printers will work. Anyway I hope to have this convention
cat-rev-text-datemmdd-longertext and the lazy dum-quikdirty.jpg methode scrutinized. instead of dum I could put IMP- or if I want it first I could put A0A - On the other forum for blender i found out I was "retarded" for putting DEC in for the date !