P: Please add Export to Parent Folder option

[kurtiskronk]

I would like to request that we add to the export options. Currently I have been using "Export to: Same folder as original photo" and then moving the sub-folder it creates in Library View, but it would be great to just have the following option:

"Export to: Parent folder of original photo"

Here's my use-case... My photography drive structure looks like this:

• Working Drive
  • Pictures
    • Clients
      • YYYY-MM-DD-ShootName
        • RAW
        • Edited-JPEGs
        • High-Resolution
        • Low-Resolution
        • Rejects

When I am editing a shoot, I begin with the RAW files. After culling, I move over all 0-star images to Rejects folder. Next, I perform all basic edits in Lightroom and I then export full-resolution full-quality JPEGs to a folder named Edited-JPEGs which currently goes under the RAW folder, then I manually move it to the parent folder in Library view. Then I do any retouching to the Edited-JPEGs in Photoshop. Once I've completed any retouching I then go back into Lightroom and export High-Resolution (smaller than full-resolution) and Low-Resolution files for my clients, which I deliver via digital download.

I would love to not have to bounce back and forth into Library mode moving folders around, it's extra unnecessary steps for me. I also do not want to manually select folders on each export, it's tedious and prone to errors with my ADHD brain.

Exporting to the parent folder with an option in the drop-down would allow me to export with fewer clicks to the desired location and would make me super happy!

[GoldingD]

I then export full-resolution full-quality JPEGs to a folder named Edited-JPEGs which currently goes under the RAW folder, then I manually move it to the parent folder in Library view.

Maybe I misunderstand, maybe a similar file structure chart for the finished file structure will help. But, why what sounds like an extra step? Why not locate "Edited-JPEGs" in the file structure location you finally move it to?

[kurtiskronk]

RAW, Edited-JPEGs, High-Resolution, Low-Resolution, and Rejects all end up in the parent folder of that shoot 'YYYY-MM-DD-ShootName'. To locate it there from the start, I'd have to pick the folder each time I edit a new shoot. It's less tedious and less accident prone to just export to current folder and create a sub-folder of the appropriate name at that time (via preset), and then just drag it. However, I'd like to eliminate that step and just have the option to make it go to the parent folder so that it creates a folder in the same directory as the original photo, beside that folder, not within it. Does that make sense?

[GoldingD]

Is this the same catalog each time? 

[kurtiskronk]

Sometimes yes, sometimes no. But every shoot gets its own parent folder within "Pictures/Clients" for example:

2023-07-31-DiazFamilyPoolside

2023-08-01-FuegoRestaurante

etc... So within each individual shoot I have those RAW, Edited-JPEGs, High-Resolution, Low-Resolution, and Rejects folders. 

[JohanElzenga]

You could consider using collections rather than physical folders. That is how Lightroom is designed. Folders are physical storage places only, not the best way to organize images. Collections and smart collections can be seen as virtual folders designed for organizing your images faster and better.

What you need is a way to quickly see the type of image you want, and collections and smart collections do just that. There is no compelling reason why these images would also have to be in different storage places.

[kurtiskronk]

I like my images organized into physical folders because I work in apps outside of just Lightroom, I deliver organized files to clients, and using collections as you suggest doesn't really address my concern in any way so far as I can tell. 

I do not want my RAW files and 3 different sizes if JPEGs all sitting in the same folder. That is incredibly annoying, and I do not want to have to sort by type or do a search for .ARW files or have to append my filenames to say -full-01, -high-01, -low-01, etc...

The simple fact is that my request would be a relatively easy addition for developers and would allow me the flexibility to easily work in the manner I wish to.