This is a lengthy post (~4500 words). I cover file names in great detail, but go much further into the differences between a literal and abstract asset management system (descriptive file names vs. not), spend many paragraphs debunking time zones, daylight time, traditional date formatting, and use 500 words to debate underscores vs. hyphens vs. spaces to break up words in your web addresses. The implications go way beyond mere file names. Read on if you’re in for a adventure . . .
I don’t like that all the articles I read on organizing your photos recommend giving them descriptive file names. The problem with files and directories is that they’re just like their non-computerized equivalents: rigid and inflexible. Your photo cannot appear under “flowers” and “macros,” because a file can only belong to one folder. Similarly, it can only have one file name, and if you fill that with keywords so you can use the Windows search to find it, the name becomes long and unwieldy. Plus, if you take a lot of photos (I’m averaging 500 a month), it’s totally impractical.
Why is it impractical? Because you’re restricted in length and taxonomy, there are no connections between files besides rigid folders and rudimentary keyword searches, and you’re adding metadata in a bad place, because the file name should be the unique and persistent identifier for the image. If you want to change all your pictures of “cars” to “automobiles,” you’re in trouble. Every time your taxonomy scheme changes, you have to change dozens of file names. This is fine if you’re the average, uninformed user: you have one copy of each photo in “My Pictures” on your hard drive, and that’s all that exists. But even then, unless you’re use batch renaming software like 1-4a rename (the biggest kludge …
