RoamingScott wrote:
I can't imagine a more obtuse and functionally useless file hierarchy than one based on parent folders that are simply single day dates, though.
Maybe you don't find that logical, yet perhaps the OP does? If it works for them, why change it? I mean, I wouldn't put photos in a folder simply named "22" inside a folder named "07" inside a folder named "2026" but that seems to be the default of some apps, such as some from Canon that I've used for scanning, etc.
By the sounds of it, maybe what the OP wants is an app that will create a dated subfolder based on the time/date metadata within the photos at the time of importing to the computer? I know Photo Mechanic can do this, either on import or when you use it to copy/move photos to another location. But as mentioned in my previous post, it's now an expensive and specialized app. I haven't looked for this capability elsewhere but I'm guessing it also exists in other apps.
FWIW, my image importing routine with Photo Mechanic is for it to put images in a dated folder where I point it to, using the app's {datesort} variable that creates a YYYYMMDD folder name, plus whatever other descriptive text I wish to include. That folder will reside as such on my working SSDs and eventually is moved to HDD cold storage where it might end up on drives dedicated to various categories such as 'jobs' 'sports' 'travel' etc. And on each of those drives would then be relevant subfolders, such as football, hockey, soccer, country names, client names, etc.
For me at least, the YYYYMMDD string is integral to my organizational thought processes. It's how I remember stuff like this. But I additionally use NeoFinder so that I can quickly also find what I need with descriptive text searches. For this reason I'm a proponent of adding caption/keyword information to individual image files.