Lightroom: Multiple Folder Locations due to caps sensitivity and full path vs mapped drives

  • 3
  • Problem
  • Updated 7 years ago
  • (Edited)
I have lightroom 3.3. My photos are stored on a NAS.

Originally i imported my folders from network location '\\server\folder'

At some point, i mounted the folder under a drive letter, and subsequently imported.

I then had two 'Folders' in the library browser.

I realized my mistake and started to use the 'update folder location' to merge them.

Now, i am importing, and it has created a new folder again, this time with a upper case first letter like "\\Server\folder" . Note the uppercase S. I dont know where its getting the uppercase letter from.

This is all quite irritating. Lightroom should be able to figure out that the folders are actually the same. I guess this involves making the UNC caps insensitive, and understanding that network shares can have full path, or be mapped via a drive lettter (at least in windows)
Photo of matin barlow

matin barlow

  • 4 Posts
  • 0 Reply Likes
  • frustrated

Posted 7 years ago

  • 3
Photo of Lee Jay

Lee Jay

  • 990 Posts
  • 132 Reply Likes
Lightroom's catalog is fundamentally tied to the OS's path at this point. I know at least one person who has railed against that approach since before LR 1, but so far the situation remains.

For me, I make absolutely sure, using the OS, that the path name of my image files remains a constant. There are several ways to do this, depending on which OS you use (I use Windows and disk management for external drives and the SUBST command for internal drives).
Photo of Beat Gossweiler

Beat Gossweiler

  • 238 Posts
  • 36 Reply Likes
I agree that LR should make UNC paths case insensitive, but this is only because of shortcomings in Windows. Windows makes a real mess out of those network shares, you can see in in Windows Explorer by accessing shares in different ways :-(

To make assigned drive letters equal to UNC paths will be to much to ask for though, IMHO. I have started ONLY using assigned drive letters because of the very fact that case sesitivity and how Windows presents the paths is a problem.

Beat
Photo of john beardsworth

john beardsworth

  • 976 Posts
  • 209 Reply Likes
With one client I've been doing exactly the opposite - switching to network addresses because the drive letters keep changing. But we've also been hit by changing cases. Whatever the cause and whatever the best solution, Lightroom should make it easy to reconnect - hence the importance of your post
http://feedback.photoshop.com/photosh...

John
Photo of matin barlow

matin barlow

  • 4 Posts
  • 0 Reply Likes
The RFC's for NETBIOS (used by SMB) indicate that at least the netbios 'name' is case insensitive.

Also, the RFC's for DNS (used by CIFS) indicate also that the host name is case insensitive.

So, the host *name* part seems straight forward, and RFC compliant, to be case insensitive.
Photo of Beat Gossweiler

Beat Gossweiler

  • 238 Posts
  • 36 Reply Likes
I've seen all different representations (for both hostname and netbios name, including the first letter being capital and the rest lowercase) in Windows 7, so I just think of it as a mess.

Beat
Photo of matin barlow

matin barlow

  • 4 Posts
  • 0 Reply Likes
Yeah, i agree its a mess.However, if lightroom always converted to the full unc path, and used caps insensitive server name, then it would make great strides into making network shares easier.
Photo of Beat Gossweiler

Beat Gossweiler

  • 238 Posts
  • 36 Reply Likes
No disagreement on this :-)

Beat
Photo of matin barlow

matin barlow

  • 4 Posts
  • 0 Reply Likes
i did a quick search, and found trivial code to convert a mapped drive, to a full UNC path (ok, its basic, but you get my point)

http://support.microsoft.com/kb/160529

So, it appears it would also be trivial to unify the folders where a person connects via mapped drive, or via full UNC.