Update (September 2009): After much consideration and much writing, I’ve developed a new workflow that I’m quite happy with. Thomas’ workflow and some of the thoughts below were very influential. Please see my new article, “How I Organize My Catalog and Why (2009 Edition).”
A few days ago, a friend sent me a copy of Thomas Hawk’s article, “My Photography Workflow 2009.” A few minutes ago, I tweeted saying that I thought this article would cause me to radically shift my personal workflow. Another friend asked what I meant by that, so I thought I’d try to address that here.
Disclaimer: This is all still a bit murky in my mind. If you’re looking for definitive answers, don’t read this. This post is more about exploring new ideas. What changes, if any, come to my personal workflow may or may not resemble what I’m discussing here. I’ll confess to being a bit nervous about posting this, since my article from last fall on how I organize my Lightroom catalog is by far the most popular thing I’ve written on this blog, and I’m now considering changing much of what I’ve written there.
So first … why am I open to even considering a radical shift in my personal workflow? Well, there’s a part of the workflow that I haven’t discussed publicly, because I haven’t been happy with it: That is, how should I segregate the best of my work (i.e. that which I wish to show) from the rest of my work (i.e. what sits locked away on a hard drive somewhere “just in case” I might need it someday)? Right now, I have two catalogs: One holds the “main” files and another is my “archive” catalog. Every so often, I physically move files from the main catalog to the archive catalog. It’s a lot of work to do this, and I haven’t been particularly happy about the way it works.
That’s why Thomas’ Step 5 (Export JPG file) caught my eye. It solves several problems that I have in my current workflow:
- The raw files wouldn’t have to move at all from one catalog to another. In my hypothetical new workflow, I’d have a catalog of all of the “source” images which would be rarely consulted, and a separate catalog of exported JPGs that contain final-form photos that I’m happy to show and share.
- As it stands now, the raw files don’t fit on my laptop. Even when I edit down to the selects, they still don’t fit comfortably. Having a JPG-only catalog of selects solves the disk-space problem.
- The act of choosing what’s in and what’s out becomes an affirmative process rather than a process that’s about rejecting photos. Why not make the selection process a happy one?
- This means the “selects” catalog is always in tip-top shape whenever I need to show someone my current work. Right now, the “main” catalog always contains some number of rough photos that haven’t been filtered out to the archive catalog.
That said, I think there are some points where I’ll differ from Thomas. As I said in my article last fall, I don’t think there are right or wrong answers; there are answers that do or don’t work for each of us individually.
The main differences that I see:
- I’ll import my photos directly into Lightroom instead of using Canon or other proprietary software.
- Unlike Thomas, I do like the DNG image format, primarily because it eliminates the need for XMP sidecars, so I’ll continue to make those conversions fairly early in my workflow.
- I’ll continue to place basic location metadata into my photos early in the workflow. This means geotagging (workflow unchanged from my November 2007 article on geotaggging) and adding basic location metadata into the appropriate IPTC fields. (FWIW, I almost always carry a handheld GPS unit with me when shooting and transfer that data to the computer whenever I import photos.)
I’m still working out many of the details. I’d love to hear your comments and suggestions.

{ 1 trackback }
{ 10 comments… read them below or add one }
Hi Eric,
Why wouldn’t you just use a collection to showcase your best work, rather than go through the rigmoral of moving JPEGs between catalogs?
Tim
More from author
It’s not just about showcasing, it’s about drawing a boundary that says: These are the photos worth further investment (keywording, publishing, copyright registration, showing to friends, keeping a copy on all of my computers, etc.), and these others (that don’t get rendered out to JPEG) are not. How do you browse across your catalog while observing that boundary?
Also … see the point I made about disk space above. Pulling out top-quality JPEGs into a distinct folder with a catalog of its own makes something that I can reasonably transfer as a whole unit between laptop and desktop. With the current “everything included” DNG-based catalog, I have to find a way to subset what goes onto the laptop, and I don’t currently have a good method for doing so.
That said, I did say at the top of this article that I’m basically thinking out loud here. I’m not committed to this approach yet, but it is appealing.
More from author
“How do you browse across your catalog while observing that boundary?”
By clicking on the collection that contains your best work?
Or assigning 5 starts to your best work and filtering or using a smart colllection?
I’m not sure that I understand your point about disk space and laptops. If you need to carry your best work to a client then that’s fine, just export your “best work” collection to a new catalog with previews only and recreate it from time to time.
But I can’t grasp the idea of maintaining a separate catalog of your best work in JPEG form just for the sake of it. You’d never want to make modifications to those JPEGs, you’d want to do that on the main catalog. So having two just seems like hard work.
I’m clearly missing something, but I don’t see what it is.
More from author
Thanks for the post, Eric. Things happened in reverse for me. Prior to LR, I did have a JPEG set—actually 2, one high res and one low—but I was never happy with having to manage them manually. What LR did was liberated me from the drudgery of having to.
To me, the LR (or LR/Photoshop) edits are my “final versions” and I only export when I need to—to JPEG or whatever format is appropriate. (The caveat being that “final” has come to mean “until software comes along that enables me to do more”, as in the case of LR coming along and pushing beyond the boundaries of what was possible before.)
Though I admit, I haven’t solved the desktop-to-laptop issue yet, and I see where JPEGs help in that case. I use an external drive and try to keep up with it, but always end up forgetting which files I’ve exported and which I haven’t. It’s almost as if I need a “catalog sync” feature to help me keep the 2 catalogs straight—my big master one and my exported JPEG one. I’m probably thinking about this wrongly.
I don’t use DNG either, because I haven’t heard a really compelling argument as to why I should add that step (and take up that disk space). My logic is unless LR stops supporting my original RAWs down the line, I have no reason to worry. Perhaps I just have my head in the sand.
More from author
I, too, am missing something… doesn’t exporting a JPG from raw, then reimporting into Lightroom defeat the whole purpose of Lightroom’s core workflow? At first glance, this sounds absolutely ridiculous, but perhaps that’s the genius and I’m just slow to catch on. I posted a comment on Thomas’s post asking for more on his thought processes here, but I don’t expect much. The guy carries around $15k worth of equipment for a simple photostroll, taking thousands of photos a day, but he geoencodes by hand? He uploads by hand? Not a very efficient workflow at all.
Anyway, back to central theme, as Tim says, just use a star rating, keywording, etc. to make your “Published Photos”, but one big hassle with that is that filters in Lightroom are local, not global. If only we could get Adobe to fix this? If only we knew someone who could actually do something about it? The perfect solution, enough to make everyone happy, is to follow the pattern for Photoshop’s “fill light” global checkbox. Then you can have them global or local, as you see fit on a per-location basis, but when you choose global, you know exactly what you’re getting and can change it in a jiffy.
More from author
Jeffrey, you’ve hit the nail on the head here: “One big hassle with that is that filters in Lightroom are local, not global.” There has been much discussion internally on this topic. Whether that changes in a future version is still up for grabs. Regardless of that outcome, I’m still using 2.3 as my production version for now. You could view the JPEG catalog as as a grossly oversized global filter.
Peter, I haven’t noticed that DNGs take up more space than the original raw files. (I don’t use the embed original file option, though. Turning that option on does add quite a bit of overhead. But I’ve never once wanted to go back to the original raw file after three years and tens of thousands of DNG conversions.) There is definitely a time cost involved in making the conversion, but once done, I find it more convenient. YMMV.
I think the main unresolved question for me in considering this workflow is whether the decision about making a photo “final form” is sticky enough that I’d be satisfied with this approach.
More from author
Some of his workflow did seem obtuse. GPSing by hand is what you do when you start out, but it quickly becomes an obsession
I use my iPhone with Trails.
Importing using the Canon software is odd as well – I can’t see its benefits. I use ImageIngester Pro, one cos of the ability to have naming presets on import. The other because of its ability to back up into 2 different places using the same folder names (whereas Lightroom calls the folder Backup of …)
Anyway, best work, I store it in a separate Catalog as a copy, but because Lightroom only allows 1 Catalog open at a time it is not an ideal way of working with the images.
More from author
A bit of a branch from the topic, but I’ll tell you a primary reason that I don’t like DNG and *do* like the sidecar XMP files: I keep copies of my files on network shares and with the XMP embedded in the DNG, I have to copy the whole 25MB+ DNG file every time I update the metadata whereas with it as a sidecar file, I just copy of a couple of hundred bytes. The difference in speed is tremendous.
You could tell me to just get a proper tool that does block-level copying rather than file-level copying but those don’t seem to be popular on Windows and I’m not interested in setting up the whole Cygwin environment just to have rsync.
More from author
As I said, YMMV. That’s a perfectly valid reason not to use DNG IMHO.
Believe me, in the early days of Lightroom’s development, there was vociferous debate on this topic, with some arguing that we should only offer the option you described.
Some choice is good.
More from author
Very interesting, Eric. I’m researching photographer’s views on Lightroom workflow because I’m just in the process of changing over from using purely PS CS3.
Thanks,
Andrew.
More from author