join south africa and (sorta) japan, use YYYY-MM-DD as a default - sorts well, zero ambiguity… at least until some joker starts popularising YYYY-DD-MM, anyway
I’m a systems guy. ISO8601 or die. Whomever decided to put the most significant digits at the end of MMDDYYYY can get fired. From a cannon. Into the sun.
Everyone talks big game about the file names but forget how important standardizing on log time stamps is too. When I’m able to pipe a bunch of logs into sort, I get so happy.
I recall writing a script that produces that 01237 with smaller digits around it for the current date. It lists the numbers that occur in the date (0, 2, 3 and 9 for 2023-09-09), the smaller digits show at which position they show up in a YYYYMMDD format (the 0 shows up on positions 2, 5 and 7)
The script has not been pushed online cause it was so dang bad
I enforce ISO 8601 for the shared storage in my office. Before I got there, files were kinda stored in all kinds of formats, but mostly month first.
I tell the person under me she can store her files in her user any way she wants, but if it goes into shared storage, it’s ISO 8601. I even have a folder in there called !Date format: YYYY-MM-DD Description to help anyone else remember.
I refuse to believe anyone does this. I think the inconsistency comes down to how people speak. "The meeting will be held on the 10th of January 2023" = 10/01/2023 but "January 10, 2023" = 01/10/2023.
I don't know how you would have to torture your brain for it to feel at home with YYYY-DD-MM.
Understandable, but the keystrokes are helpful for human readable. I always have the “Suspicions Fry eyes” when I want to read 20230809 in a lot of files.
I actually need to standardize my code. I’ve got “learning F2” as something I want to do soon. The goal: use the exif data of my pictures to create [date in ISO 8601] - [original filename].[original file type termination]
So a picture taken the third of march 2022 titled “asdf.jpg” would become “2022-3-3 - asdf.jpg”
If you’re on Linux exiftool can get the creation date for you: exiftool -p ‘$CreateDate’ -d ‘%Y-%m-%d’ FILENAME, and you could run tgat in a loop over your files, something like:
<span style="color:#323232;">mkdir -p out
</span><span style="color:#323232;">for f in *.jpg
</span><span style="color:#323232;">do
</span><span style="color:#323232;">createdate=$(exiftool -p '$CreateDate' -d '%Y-%m-%d' "${f}")
</span><span style="color:#323232;">cp -p "${f}" "out/${createdate} - ${f}"
</span><span style="color:#323232;">done
</span>
Obviously don’t justbgo running code some stranger just posted on the internet, especially as I haven’t tested it, but that should copy images from the current directory to a subdirectory called ‘out’ with the correct filenames.
I don’t see any HTML when I look at that comment from Lemmy, but kbin seems to make a real mess of rendering code blocks. Basically that bit had a few lines of code they could yse to do what they wanted.
I’m using NixOS. Ext4 filesystem. As to language, I’m not entirely sure what you mean. If you refer to the character set in the filenames, I think there are no characters that deviate from the English alphabet, numbers, dashes, and underscores.
Oh ok so you’re more so working with folder structure etc, so bash for when you plug-in a card?
I’m thinking in more programmatic terms, there’s definitely some bash scripting you can execute. Or just go balls out and write a service that executes on systemctl
lemmy.ml
Hot