Skip to main content
Known Participant
March 30, 2024
Question

Import not reflecting parent folder properly

  • March 30, 2024
  • 3 replies
  • 338 views

Hi - I need help determining if I am doing something wrong, if something has changed or if I'm hitting a bug with Lightroom Classic.

When I import picutures, LRC is not reflecting the proper catalog folder structure (speciifcally, the imported pictures only show the folder the pictures are in but none of the parents are refected - this is causing the folder to be out of position in the LRC folder structure navigation panel).  SHOW PARENT FOLDER and UPDATE FOLDER LOCATION have not helped with fixing this problem.  I believe I'm using the same import process I've used for years but perhaps something has changed?  Process described below:

1. Store pictures on disk - structure is "Personal/YYYY/MM/DESC"

2. Import ADD into LRC

The result is the LRC folder strucutre shows the DESC folder as an orphan.  I can use SHOW PARENT FOLDER and UPDATE FOLDER LOCATION iteratively until I get to the YYYY folder but that structure is never shown under the parent "Personal".

Any input on what I should do differently is appreciated - all I want to do is import pictures into the catalog so the catalog folder structure matches the disk structure.  Screen shots attached showing after import, after SHOW PARENT FOLDER and after UPDATE FOLDER LOCATION.

This topic is closed to new replies. Start a new post to keep the conversation going.

3 replies

Known Participant
March 30, 2024

QUICK CLARIFYING UPDATE - this process used to work for me.  I'm not sure exactly when it stopped but I've been fighting this battle for at least months now.  Thanks

JohanElzenga
Community Expert
Community Expert
March 31, 2024

This is the 'Capitalization problem'. Here's an explanation and how to solve it: 

https://www.lightroomqueen.com/capitalization-catalog-error/

 

-- Johan W. Elzenga
Known Participant
April 1, 2024

@JohnElzenga great catch.  I asctually knew have heard of this but didn't catch it because the at fault folder was above the  last visible parent.  All better.  Thanks!