File/process image management

[malathan]

I asked this question (or similar) a year ago, but would like to requery how others handle image files as they progress through post-processing. I have been revising my process this year, but not sure if I have it fully ironed out yet. Looking for ideas that I may not have considered.

Question: How do you handle/store the original image (raw), any intermediate images (dng from LR's denoise or 3rd party editors), and final image?

My organization that I have come up with...

• Moved from \yyyy\yyyy-mm-dd to more of a category order. Unless trip call for it, or multiple trips in same year, I am combining days together to one folder
  • [Trip] Canada
    • [Trip] Banff, BC
      • 2015 - [Trip] Banff, BC
    • [Trip] Vancouver-Victoria, BC
      • 2014 - [Trip] Vancouver-Victoria, BC
      • 2018 - [Trip] Vancouver-Victoria, BC
  • [Trip] Oregon
  • • [Trip] Japanese Garden, OR
      • 2022 - [Trip] Japanese Garden, OR
      • 2023 - [Trip] Japanese Garden, OR
        • 2023-10-19
        • 2023-10-27
      • 2024 - [Trip] Japanese Garden, OR
    • [Trip] Depoe Bay, OR
      • ...
  • Family
    • ...

Within these folders, I keep

• Original (raw)
• intermediate file (if any...very few)
• Final jpg (suffixed with "Final <app>")

IE:

• DCM 2022-10-09 14-01-20 #123.cr3
• DCM 2022-10-09 14-01-20 #123 - NR.cr3
• DCM 2022-10-09 14-01-20 #123 - Final LRC.cr3

Using color labels to identify image status...

• Red = Edited...ready to generate final
• Yellow = Final generated
• Blue = Panorama/Focus/HDR parts.

Ratings are just normal preferences... 1= "eh" (don't delete, but so so) and 5 = "wow". Most usually are 2-3, with few 4's. Trying to spend more time moving 1's to rejects/deletes.

Lastly, I use my NAS for backup, so all images are copied to it (using SyncBack). Additionally, I use the photo app on the nas (synology) to centralize "final" images and have a backup routine that copys only files with " - final xxx" to a special folder that will mirror my structure above, thus I have a folder ONLY with final images.

--
- Malathan

 

[grsnovi]

...I didn't save my raws after I got the desired jpg.

Since I recently got a new laptop with a decent graphics card and both DxO PL8 and Topaz Photo AI, there are shots that I would have liked to re-process.

So I'm rethinking my strategy.

I usually create a folder for a specific day's shoot saved within the specific month within the specific year. Within that folder I'll create a raw sub-folder. I'll drag the raws to that folder and the jpgs (from the camera) to the dated folder and process from the raw folder and over-write the jpg in the jpg folder.

I will then save "keeper" jpg's by subject into another folder structure.

I'm manually backing up to a set of usb drives.

 

[ishwanu]

I copy source files to temporary folders on the desktop where I cull and edit at my leisure. When I eventually finish a photo of group of photos I export final JPEGs. Those get stored on my NAS chronologically in year/month folders that are also copied to redundant disk storage. The temporary folders and source files are then deleted. I use a DAM to do auto or manual keywording and face recognition on the NAS collection. I don't apply ratings.

 

[malathan]

...

IE:

• DCM 2022-10-09 14-01-20 #123.cr3
• DCM 2022-10-09 14-01-20 #123 - NR.cr3
• DCM 2022-10-09 14-01-20 #123 - Final LRC.cr3

...

Just notice typo. Should be

• DCM 2022-10-09 14-01-20 #123.cr3
• DCM 2022-10-09 14-01-20 #123 - NR.dng
• DCM 2022-10-09 14-01-20 #123 - Final LRC.jpg

 

[gscotten]

I am so happy that I use LrC and only have to keep my original raw images.

 

[malathan]

I am so happy that I use LrC and only have to keep my original raw images.

Within LrC, you can share collections with others, sync those collections to LR (and mobile) and such. Going this route, it is MUCH easier to keep only raws and let LR do the rest of the lifting for you. Agree 101%.

But what I have found is if you do switch apps (my headache and curse this year), then you need to pull all those final images out (export) of the other app. And there are a few effects in LrC that I can't reproduce without jumping into another app (as much as I curse On1 and am fleeing as the main processing app, their effects are quite good and will still use their dynamic contract, sunshine, and glow effect on occasion). Thus my " - Final On1.jpg" outputs and general thought I should keep a final image outside of the app...just in case.

 

[dj_paige]

May I ask what parts of this workflow and image management do you feel could be improved somehow? What improvements are you looking for — fewer steps, same number of steps but faster, different folder organization strategy, totally out of the box ideas?

 

[Zeee]

This has always been my folder structure. In the each year I create a folder and name it based on the event and date. If I was a working pro I might add a new folder for every month within that year. I tried that for my hobby stuff but it became a pain. I can open a folder and see all my shoots for the whole year.

For any 3rd party app and Deniose AI, I stack the DNF or TIFF beside the original RAW file. This included sending a file to PS and back.

For mass exports like shooting an event that has a lot of files. Not all went to a 3rd party apps or PS. There was no Adobe Denoise back then so I'm inlcuding it for this conversation. I devised a way to only export those edited DNG and TIFF files and not the original RAW files. If I sent a file out for additional editing, it would have been an improvement over the original RAW file so I'd only want to export it, not the RAW file. There would have been two copies of the same file.

If I was a working pro I'd likely separate Work and Play. I would not have a separate catalogues. I'd set those two up as Root folders just below My RAW Collection.





--
I roll with pleasing colour

 

[malathan]

May I ask what parts of this workflow and image management do you feel could be improved somehow? What improvements are you looking for — fewer steps, same number of steps but faster, different folder organization strategy, totally out of the box ideas?

Good quesiton dj_paige. As I transitioned from one editor to another this year, this is what started me down the path of revisiting how I manage files, including exports. Prior I kept edits within the app and just fired it off, but not viable if switching.

What I am after is just to see how my approach, which I think will work good for my needs, matches others. I have seen others keep Raws in completely separate folders from intermediate/final images, archiving Raws fully off the computer. Others keep them together. Others rely more on generating final images and storing them in the cloud or other location, some keep them local, and some don't generate final images at all but view them through the editor as needed.

I like to learn and find it interesting to see what approaches others take, if it is something that I didn't think of and such.

 

[Zeee]

May I ask what parts of this workflow and image management do you feel could be improved somehow? What improvements are you looking for — fewer steps, same number of steps but faster, different folder organization strategy, totally out of the box ideas?

Good quesiton dj_paige. As I transitioned from one editor to another this year, this is what started me down the path of revisiting how I manage files, including exports. Prior I kept edits within the app and just fired it off, but not viable if switching.

What I am after is just to see how my approach, which I think will work good for my needs, matches others. I have seen others keep Raws in completely separate folders from intermediate/final images, archiving Raws fully off the computer. Others keep them together. Others rely more on generating final images and storing them in the cloud or other location, some keep them local, and some don't generate final images at all but view them through the editor as needed.

Yes. Both files are there together so I know where they are. DXO does something I don't like and can't control unless I delete it. It creates its own collection when files come from PR or PL. When Adobe introduced Denoise AI, I could hardly wait to get rid of all that. That's just a personal thing. I'm sure it does not bother others.

I like to learn and find it interesting to see what approaches others take, if it is something that I didn't think of and such.

--
I roll with pleasing colour

 

[dj_paige]

May I ask what parts of this workflow and image management do you feel could be improved somehow? What improvements are you looking for — fewer steps, same number of steps but faster, different folder organization strategy, totally out of the box ideas?

Good quesiton dj_paige. As I transitioned from one editor to another this year, this is what started me down the path of revisiting how I manage files, including exports. Prior I kept edits within the app and just fired it off, but not viable if switching.

I suppose the answer I would give depends on what editor you are switching to. Editors that have DAM capabilities in the same program would probably result in different answers from me than editors without DAM capabilities in the same program.

What I am after is just to see how my approach, which I think will work good for my needs, matches others. I have seen others keep Raws in completely separate folders from intermediate/final images, archiving Raws fully off the computer. Others keep them together. Others rely more on generating final images and storing them in the cloud or other location, some keep them local, and some don't generate final images at all but view them through the editor as needed.

I see no need to keep RAWs separate from other files. Your operating system, and any software with a DAM, can distinguish RAW from other files, so no need for the multitudes of RAW-only folders.

--
Paige Miller

 

[Zeee]

May I ask what parts of this workflow and image management do you feel could be improved somehow? What improvements are you looking for — fewer steps, same number of steps but faster, different folder organization strategy, totally out of the box ideas?

Good quesiton dj_paige. As I transitioned from one editor to another this year, this is what started me down the path of revisiting how I manage files, including exports. Prior I kept edits within the app and just fired it off, but not viable if switching.

I suppose the answer I would give depends on what editor you are switching to. Editors that have DAM capabilities in the same program would probably result in different answers from me than editors without DAM capabilities in the same program.

What I am after is just to see how my approach, which I think will work good for my needs, matches others. I have seen others keep Raws in completely separate folders from intermediate/final images, archiving Raws fully off the computer. Others keep them together. Others rely more on generating final images and storing them in the cloud or other location, some keep them local, and some don't generate final images at all but view them through the editor as needed.

I see no need to keep RAWs separate from other files. Your operating system, and any software with a DAM, can distinguish RAW from other files, so no need for the multitudes of RAW-only folders.

I agree. Keep it simple. You can also use the metadata in the Library Grid view to select what you want to see. A few weeks ago I was doing some in there and someone unintentionally changed a parameter and thought I deleted a bunch of files. The DAM and Database is excellent.

 

[Barleyman]

I keep it simple.

Rule 1: Once I copy my Raw from the camera onto my Storage array, I never look at, or care about, the file outside of Lightroom. I don't fiddle with it, move it, etc. If I do NR, or PS edits, that file gets put in and left in the same folder (and is stacked in LR).

My RAW storage is set up in a folder hierarchy by Year and Month. Every once in a while I will create a folder for exceptional situations, like time lapse, etc.

My folders in Lightroom mimic the Storage hierarchy. It's a one to one folder structure that is easy to traverse. Every once in a while, i will "Sync" the whole year to makes sure I imported everything into LR (I am retentive enough that this usually doesnt find anything).

My Output (JPEG) storage is a bit different. I have it by Year, then "event". The folder names always start with MMYY, e.g. 2412 Christmas Parade). I sometimes will have a sub folder in the event folder for shots from other devices that I may edit and include in the event folder (e.g. Drone JPEGS, PHONE HEIC, etc).

I use the Lightroom tags, people, and collections for cross references, so it is usually pretty quick to find something if I need to. Since LR exports to tags, external search tools can also find them

 

[Barleyman]

I only export Flagged items from LrC. Since I also stack in LrC, I only get the top image to be exported, so round trips to NR and PS don't impact my export.

 

[Zeee]

I keep it simple.

Rule 1: Once I copy my Raw from the camera onto my Storage array, I never look at, or care about, the file outside of Lightroom. I don't fiddle with it, move it, etc. If I do NR, or PS edits, that file gets put in and left in the same folder (and is stacked in LR).

My RAW storage is set up in a folder hierarchy by Year and Month. Every once in a while I will create a folder for exceptional situations, like time lapse, etc.

My folders in Lightroom mimic the Storage hierarchy. It's a one to one folder structure that is easy to traverse. Every once in a while, i will "Sync" the whole year to makes sure I imported everything into LR (I am retentive enough that this usually doesnt find anything).

That is important to point out. One of the top mistakes or misunderstandings with LrC and the catalogue system. LrC mimics your storage hierarchy as would any other software if you pointed it there. It does not create its own or create anther set of duplicate files. This sometimes leads to someone disliking the catalogue system for not the right reasons.

Anthony Morganti has an excellent video for anyone starting out with LrC.

My Output (JPEG) storage is a bit different. I have it by Year, then "event". The folder names always start with MMYY, e.g. 2412 Christmas Parade). I sometimes will have a sub folder in the event folder for shots from other devices that I may edit and include in the event folder (e.g. Drone JPEGS, PHONE HEIC, etc).

I use the Lightroom tags, people, and collections for cross references, so it is usually pretty quick to find something if I need to. Since LR exports to tags, external search tools can also find them