"Automatic organization" on a case-sensitive filesystem - not really "portable"

Bug
1

PS for Docker, 2024.3.3-beta

Given a source volume with files like:

.../dir1/photo.jpg
.../dir2/photo.JPG

Note the “different” file extensions (but I doubt the problem is exclusive to extensions).
Say it’s on NTFS - a case-insensitive filesystem (wouldn’t allow those 2 files in the same folder) but a case-preserving one nonetheless (if saved in different folders, each file keeps the exact case it was created with).
That’s the situation I encountered… but, I don’t know, perhaps the same would occur on a Linux-style (case-sensitive) filesystem (then, possible even with multiple files from a single folder).

And assuming:

  • the two files were both “captured” on the same day…
  • we run “automatic organization”…
  • the files are “unique” (maybe slightly different variants of the same photo, or maybe entirely different photos - but either way PS “wants” to keep both files in its library)…
  • the target volume (PS library “originals”) is on a case-sensitive filesystem

Expected Behavior

“Different files taken on the same day that share the same name will be given a unique number suffix.” – from Automatic library organization.

Current Behavior

No unique number given to those auto-organized file names.

Here’s one example where we can easily see this (when those are “variants” of the same photo):
image

The Bug

Now, PS works fine - treats the files as separate or as one, as it’s supposed to.
All good so far. So, what is the bug, you may ask…

Well, one of the main “selling points” are supposed to be Portable libraries!
And you can’t easily “move” a folder with such files from a case-sensitive filesystem to a case-insensitive one.

I guess you can rename the conflicting files when copying them to the new (case-insensitive) filesystem… Some tools might even do it automatically if you’re lucky. Then, first time PS doing ‘sync’ on the new filesystem, it would automatically link to the renamed files (right? I have yet to confirm that).
But still, wouldn’t it be better if “auto-org” just assumed the library is case-insensitive even if it isn’t - adding those unique numbers even if they aren’t technically necessary in its current environment?

2

Thanks got taking the time to explain this so clearly!

I agree that this is a bug. Although I take care to normalize paths within PhotoStructure’s internal directory hierarchies, and template-generated directories within the originals directory, I’d not thought of this collision issue.

I initially thought that I would need to make a setting to gate this behavior so users can retain current behavior, but every added setting is additional complexity.

1 Like
3

So, here’s a poll: please react to this post with a thumbs-up if you want a new setting to preserve the current behavior, and a thumbs-down if you think a setting is unnecessary (and then libraries will always be properly portable)

(If you feel strongly one way or another, please reply and explain: assume I missed your use case!)

(Also, I think I’d like to skip the setting if no one presents a good reason otherwise)

  • Matthew missed the option in the dropdown
  • Matthew was just trolling nuc
  • Matthew prefers emoji over all other interactions because dad
0 voters
4

Where are polls permitted?

  • Only on new topics, not in replies
  • Not in new topics, only in replies
  • Both in new topics and replies
0 voters
2 Likes