LR collections and post-archival workflow

[andreiz]

I am in the process of figuring out my LR-based workflow and there are a couple of issues that I am struggling with and would appreciate any insight into.

1. What kind of collection hierarchy seems to work well? I definitely don't want to have a flat namespace where there are only top level collections and each one contains a single project. So I could organize it chronologically as "Year > Month > Project" or perhaps topically as "Travel > Europe > Paris". But I'm afraid that without rigidly defined topics/geographies I will have a mess on my hands again. Hence, I'm leaning towards chronological organization, but wanted to solicit opinions on this.

2. Let's say my process is this: import the RAW images and rename them, do ratings and trashing of unusable ones, add metadata, do basic editing in Develop module, generate Web gallery (to derivatives folder or elsewhere), transfer the RAW originals folder to archive and backup. What happens if I want to take a couple of images from this folder in a couple of months and try some other editing approaches in Develop? The folder is already backed up, so I'd rather not mess with it. I can't use Virtual Copy since that information is embedded in the XMP or DNG (which is backed up). Do I copy these images to derivatives folder and work from there? This is possible, but means that I'd have to keep originals and derivatives in the same catalog so that I can have a unified view of the variations of the original photos. Has anyone found a better approach?

Thanks for your help,

-Andrei

[Ken]

1. What kind of collection hierarchy seems to work well? I definitely don't want to have a flat namespace where there are only top level collections and each one contains a single project. So I could organize it chronologically as "Year > Month > Project" or perhaps topically as "Travel > Europe > Paris". But I'm afraid that without rigidly defined topics/geographies I will have a mess on my hands again. Hence, I'm leaning towards chronological organization, but wanted to solicit opinions on this.

Hi Andrei,

As LR should automiatically pick up the dates form the images, I see no reason to create a chronological collection.  I would think that a topical collection would be very useful, and it could be expanded as needed.  For example, why not just start with a top level of: people, places, things and events.  You can fill the levels below as the need arises.

--Ken

[andreiz]

Hi Andrei,

As LR should automiatically pick up the dates form the images, I see no reason to create a chronological collection.  I would think that a topical collection would be very useful, and it could be expanded as needed.  For example, why not just start with a top level of: people, places, things and events.  You can fill the levels below as the need arises.

--Ken

Because I'd rather keep each shoot (project) separate. I guess I could create a collection based on Find command using certain keywords and have two parallel hiearchies..

-Andrei

[Ken]

Hi Andrei,

As LR should automiatically pick up the dates form the images, I see no reason to create a chronological collection.  I would think that a topical collection would be very useful, and it could be expanded as needed.  For example, why not just start with a top level of: people, places, things and events.  You can fill the levels below as the need arises.

--Ken

Because I'd rather keep each shoot (project) separate. I guess I could create a collection based on Find command using certain keywords and have two parallel hiearchies..

-Andrei

Why not just import each shoot into its own folder?  Unless you do more than one shoot per day, this will allow you some discretion.  Remember, you can call up images in LR by folder as well as by collection.

--Ken

[andreiz]

Why not just import each shoot into its own folder?  Unless you do more than one shoot per day, this will allow you some discretion.  Remember, you can call up images in LR by folder as well as by collection.

--Ken

They will be in their own folders. But since I'm following the bucket approach from the book, these folders will be under something like Originals\ORG_003_20071220\SF_Dec_Meetup. This is great for backups, but hardly the best organization for browsing your collection.

-Andrei

[Ken]

I would still use the topical layout that I described earlier.  Under events, for example, you could create a collection for each shoot and give it a name that works for you.  The beauty of collections is that they are quite flexible and they can incorporate more than one means of (virtually) arranging your images.  In short, your collections can encompass a casual organization like a collection for each shoot as easily as it can resemble a tightly structured hierarchy.  The main thing to remember is to work with something like a very loose top level organization, and create as you need collections.  Do not try to account for everything at once (although giving some advance thought to the matter is certainly wise).  Its not necessary, and is probably a time vampire to best avoid.  Look at it this way, if you had to use a highly structured hierarchy, it would most likely be evident to you by now.  Good luck!

--Ken

[andreiz]

2. Let's say my process is this: import the RAW images and rename them, do ratings and trashing of unusable ones, add metadata, do basic editing in Develop module, generate Web gallery (to derivatives folder or elsewhere), transfer the RAW originals folder to archive and backup. What happens if I want to take a couple of images from this folder in a couple of months and try some other editing approaches in Develop? The folder is already backed up, so I'd rather not mess with it. I can't use Virtual Copy since that information is embedded in the XMP or DNG (which is backed up). Do I copy these images to derivatives folder and work from there? This is possible, but means that I'd have to keep originals and derivatives in the same catalog so that I can have a unified view of the variations of the original photos. Has anyone found a better approach?

Anyone have any suggestions regarding this second part?

-Andrei