<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Lightroom 2 Technique: How I Organize My Catalog and Why (2009 Edition)</title>
	<atom:link href="http://blog.ericscouten.com/2009/09/lightroom-2-technique-how-i-organize-my-catalog-and-why-2009-edition/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ericscouten.com/2009/09/lightroom-2-technique-how-i-organize-my-catalog-and-why-2009-edition/</link>
	<description>The photography, travel, and technology blog of Eric Scouten</description>
	<lastBuildDate>Sat, 13 Mar 2010 05:59:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Eric</title>
		<link>http://blog.ericscouten.com/2009/09/lightroom-2-technique-how-i-organize-my-catalog-and-why-2009-edition/#comment-5584</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Sat, 13 Mar 2010 05:59:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=349#comment-5584</guid>
		<description>&quot;Do Not Show&quot; does not have any special meaning to Lightroom. I only use it as my own convention to steer me away from photos that don&#039;t represent me well.</description>
		<content:encoded><![CDATA[<p>&#8220;Do Not Show&#8221; does not have any special meaning to Lightroom. I only use it as my own convention to steer me away from photos that don&#8217;t represent me well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Smith</title>
		<link>http://blog.ericscouten.com/2009/09/lightroom-2-technique-how-i-organize-my-catalog-and-why-2009-edition/#comment-5582</link>
		<dc:creator>Justin Smith</dc:creator>
		<pubDate>Fri, 05 Mar 2010 07:34:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=349#comment-5582</guid>
		<description>Eric-Thank you much for your reply. 

I think I have finally figured out the answer I was looking for, though. My problem was I tried to read all these tutorials before I started working with Lightroom. As nice as that was with the initial setup ideas-I&#039;ve finally come to realize that I just didn&#039;t understand all of what was being said. There are many parts of this post that I didn&#039;t fully grasp, until I had played with the software a bit more. 

Going forward, I will continue to read articles as such, but understand that I might have to toy around before I fully understand what they are getting at. 

That being said, I just wanted to let you know that I&#039;m stealing your catalog names, and running with them! RAW, selects, etc-that just perfectly describes the way I wanted to separate my photos. I had a really hard time grasping how the files went from Incubator to RAW, but I finally figured out you import them into RAW, instead of exporting them from Incubator. 3 weeks invested so far, and many more to go before my selects is fully built!</description>
		<content:encoded><![CDATA[<p>Eric-Thank you much for your reply. </p>
<p>I think I have finally figured out the answer I was looking for, though. My problem was I tried to read all these tutorials before I started working with Lightroom. As nice as that was with the initial setup ideas-I&#8217;ve finally come to realize that I just didn&#8217;t understand all of what was being said. There are many parts of this post that I didn&#8217;t fully grasp, until I had played with the software a bit more. </p>
<p>Going forward, I will continue to read articles as such, but understand that I might have to toy around before I fully understand what they are getting at. </p>
<p>That being said, I just wanted to let you know that I&#8217;m stealing your catalog names, and running with them! RAW, selects, etc-that just perfectly describes the way I wanted to separate my photos. I had a really hard time grasping how the files went from Incubator to RAW, but I finally figured out you import them into RAW, instead of exporting them from Incubator. 3 weeks invested so far, and many more to go before my selects is fully built!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl-Erik</title>
		<link>http://blog.ericscouten.com/2009/09/lightroom-2-technique-how-i-organize-my-catalog-and-why-2009-edition/#comment-5581</link>
		<dc:creator>Carl-Erik</dc:creator>
		<pubDate>Tue, 02 Mar 2010 21:42:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=349#comment-5581</guid>
		<description>How do you use the red &quot;do not show&quot; label? Is there a way to make LR not show a certain color by default? Or do you simply have some sort of Smart Collection that shows all labels except the red one?</description>
		<content:encoded><![CDATA[<p>How do you use the red &#8220;do not show&#8221; label? Is there a way to make LR not show a certain color by default? Or do you simply have some sort of Smart Collection that shows all labels except the red one?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://blog.ericscouten.com/2009/09/lightroom-2-technique-how-i-organize-my-catalog-and-why-2009-edition/#comment-5578</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Tue, 16 Feb 2010 02:18:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=349#comment-5578</guid>
		<description>Leslie, thanks again for sharing your experiences. It&#039;s very helpful for all of us to hear the different ways in which people use our products as we think about how we&#039;ll adapt and update in the future.

As noted before, I can&#039;t really say much about our future plans, but know that we hear you loud and clear.</description>
		<content:encoded><![CDATA[<p>Leslie, thanks again for sharing your experiences. It&#8217;s very helpful for all of us to hear the different ways in which people use our products as we think about how we&#8217;ll adapt and update in the future.</p>
<p>As noted before, I can&#8217;t really say much about our future plans, but know that we hear you loud and clear.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://blog.ericscouten.com/2009/09/lightroom-2-technique-how-i-organize-my-catalog-and-why-2009-edition/#comment-5577</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Tue, 16 Feb 2010 02:15:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=349#comment-5577</guid>
		<description>Hi Justin, I&#039;ll admit that I&#039;ve glossed over that question a bit. The reason is that I use a source-control system for moving files from one computer to another. (See &lt;a href=&quot;http://blog.ericscouten.com/2006/07/it-just-works-perforce-as-a-personal-backup-strategy/&quot; rel=&quot;nofollow&quot;&gt;my article on Perforce as a backup strategy&lt;/a&gt; from 2006.)

I don&#039;t say too much about this these days because I think Perforce is too difficult to administer and understand for most users. (If you are a programmer or hard-core computer geek, you would be the potential exception to that rule.)

In place of that, I would look for software that can keep an entire folder tree in sync across two or more computers. I&#039;m sorry to say that I don&#039;t have any specific recommendations here because I&#039;ve been using Perforce in that role for many years.</description>
		<content:encoded><![CDATA[<p>Hi Justin, I&#8217;ll admit that I&#8217;ve glossed over that question a bit. The reason is that I use a source-control system for moving files from one computer to another. (See <a href="http://blog.ericscouten.com/2006/07/it-just-works-perforce-as-a-personal-backup-strategy/" rel="nofollow">my article on Perforce as a backup strategy</a> from 2006.)</p>
<p>I don&#8217;t say too much about this these days because I think Perforce is too difficult to administer and understand for most users. (If you are a programmer or hard-core computer geek, you would be the potential exception to that rule.)</p>
<p>In place of that, I would look for software that can keep an entire folder tree in sync across two or more computers. I&#8217;m sorry to say that I don&#8217;t have any specific recommendations here because I&#8217;ve been using Perforce in that role for many years.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://blog.ericscouten.com/2009/09/lightroom-2-technique-how-i-organize-my-catalog-and-why-2009-edition/#comment-5576</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Tue, 16 Feb 2010 02:05:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=349#comment-5576</guid>
		<description>I wrote back to Chuck privately by e-mail earlier, but thought I would share the answer to his most recent question (how to delete -2.jpg files). When viewing the library grid for All Photographs (use a different source if you want to limit the scope of the search), call up the search tool (Cmd-F). In the filter bar, set the popup menus as follows: select Filename (instead of the usual All Searchable Text), Ends With (instead of the usual Contains All), and then enter the text &quot;-2.jpg&quot;. Now you can Select All and Delete photos.</description>
		<content:encoded><![CDATA[<p>I wrote back to Chuck privately by e-mail earlier, but thought I would share the answer to his most recent question (how to delete -2.jpg files). When viewing the library grid for All Photographs (use a different source if you want to limit the scope of the search), call up the search tool (Cmd-F). In the filter bar, set the popup menus as follows: select Filename (instead of the usual All Searchable Text), Ends With (instead of the usual Contains All), and then enter the text &#8220;-2.jpg&#8221;. Now you can Select All and Delete photos.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leslie Nicole</title>
		<link>http://blog.ericscouten.com/2009/09/lightroom-2-technique-how-i-organize-my-catalog-and-why-2009-edition/#comment-5574</link>
		<dc:creator>Leslie Nicole</dc:creator>
		<pubDate>Tue, 09 Feb 2010 09:31:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=349#comment-5574</guid>
		<description>Back again. Eric, I wanted to share a realization based on my own needs to provide a perspective.

After using Lightroom now for around 6 months, I&#039;m looking again at my workflow. Just spent a lot of time looking at multiple sites examining various methods from the All One Catalog zealots to the Catalog for each shoot Camp. I sat down and made a Mind Map of my own needs. I was all ready to start a multiple catalog workflow based fairly closely to yours, when I suddenly realized something.

My initial thinking for multiple catalogs would be: 1. My internally shot &quot;stock parts&quot; textures, objects, etc. I thought, no brainer - that&#039;s one catalog. Then I thought of catalogs for 2. dog photography, 3. family, 4. Fine Art, including, still life, landscape, etc. 

I do a lot of Post Production, montages, textures, etc. I also sometimes take an image into Painter to work on. So what happens if I make a photograph of a dog montaged with a Landscape, textures applied and then edited in Painter? (That may sound awful, but turned out quite nice.) That would include 3 different catalogs. Will I be opening and closing catalogs trying to find the images I need for the montage? What then happens to the derivative Montage?

I&#039;ve realized that everyone I&#039;ve been studying does pretty much &quot;straight&quot; photography. I don&#039;t shoot something, process, pick best and then file it. (For the most part.) I want my entire body of work available to pillage and create new visions. I also don&#039;t heavily edit to final choices. I&#039;ve found that often an image that wouldn&#039;t be a final pick on it&#039;s own, works quite nicely for something else. So, If I do one catalog for all of the above, even minus family photos, it would be really large. As much as the &quot;All One Catalog&quot; advocates claim this is fine, it doesn&#039;t make sense. My system is already straining, so what happens years from now?

So, I want to put another plea in, Eric please convey the need for ease of use with multiple catalogs. (Look at Cumulus!)

Second, I need to start visiting the sites of those who do photo manipulation to see how they are using Lightroom.

It&#039;s pretty cool to see how many workflows there are out there. It really is all about what works for you. Your workflow gave me a lot of important elements to consider and I&#039;m sure I&#039;ll be using some of it in my own workflow.</description>
		<content:encoded><![CDATA[<p>Back again. Eric, I wanted to share a realization based on my own needs to provide a perspective.</p>
<p>After using Lightroom now for around 6 months, I&#8217;m looking again at my workflow. Just spent a lot of time looking at multiple sites examining various methods from the All One Catalog zealots to the Catalog for each shoot Camp. I sat down and made a Mind Map of my own needs. I was all ready to start a multiple catalog workflow based fairly closely to yours, when I suddenly realized something.</p>
<p>My initial thinking for multiple catalogs would be: 1. My internally shot &#8220;stock parts&#8221; textures, objects, etc. I thought, no brainer &#8211; that&#8217;s one catalog. Then I thought of catalogs for 2. dog photography, 3. family, 4. Fine Art, including, still life, landscape, etc. </p>
<p>I do a lot of Post Production, montages, textures, etc. I also sometimes take an image into Painter to work on. So what happens if I make a photograph of a dog montaged with a Landscape, textures applied and then edited in Painter? (That may sound awful, but turned out quite nice.) That would include 3 different catalogs. Will I be opening and closing catalogs trying to find the images I need for the montage? What then happens to the derivative Montage?</p>
<p>I&#8217;ve realized that everyone I&#8217;ve been studying does pretty much &#8220;straight&#8221; photography. I don&#8217;t shoot something, process, pick best and then file it. (For the most part.) I want my entire body of work available to pillage and create new visions. I also don&#8217;t heavily edit to final choices. I&#8217;ve found that often an image that wouldn&#8217;t be a final pick on it&#8217;s own, works quite nicely for something else. So, If I do one catalog for all of the above, even minus family photos, it would be really large. As much as the &#8220;All One Catalog&#8221; advocates claim this is fine, it doesn&#8217;t make sense. My system is already straining, so what happens years from now?</p>
<p>So, I want to put another plea in, Eric please convey the need for ease of use with multiple catalogs. (Look at Cumulus!)</p>
<p>Second, I need to start visiting the sites of those who do photo manipulation to see how they are using Lightroom.</p>
<p>It&#8217;s pretty cool to see how many workflows there are out there. It really is all about what works for you. Your workflow gave me a lot of important elements to consider and I&#8217;m sure I&#8217;ll be using some of it in my own workflow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Smith</title>
		<link>http://blog.ericscouten.com/2009/09/lightroom-2-technique-how-i-organize-my-catalog-and-why-2009-edition/#comment-5573</link>
		<dc:creator>Justin Smith</dc:creator>
		<pubDate>Tue, 09 Feb 2010 06:05:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=349#comment-5573</guid>
		<description>I&#039;m sure you covered this, but I&#039;m either missing it, or just not quite understanding it. I&#039;m looking to do a setup that is nearly identical to yours. Slightly different folder layouts, but that seems to be irrelevant.  Where I get lost on your setup, is how you are taking all the photos from your laptop, ending up with all of those on the desktop, and just your selects on the laptop. I&#039;m with you on exporting to the selects, but then I am just not seeing how you end up with all the RAW&#039;s on the desktop. Help please?</description>
		<content:encoded><![CDATA[<p>I&#8217;m sure you covered this, but I&#8217;m either missing it, or just not quite understanding it. I&#8217;m looking to do a setup that is nearly identical to yours. Slightly different folder layouts, but that seems to be irrelevant.  Where I get lost on your setup, is how you are taking all the photos from your laptop, ending up with all of those on the desktop, and just your selects on the laptop. I&#8217;m with you on exporting to the selects, but then I am just not seeing how you end up with all the RAW&#8217;s on the desktop. Help please?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: René Damkot</title>
		<link>http://blog.ericscouten.com/2009/09/lightroom-2-technique-how-i-organize-my-catalog-and-why-2009-edition/#comment-5572</link>
		<dc:creator>René Damkot</dc:creator>
		<pubDate>Fri, 05 Feb 2010 11:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=349#comment-5572</guid>
		<description>One thing I am missing in LR2 is a &quot;find missing folders&quot; and/or &quot;find missing files.

Now I have to (slowly, since I need to wait for the screen refresh) scroll through 15k+ images to see whether or not some are missing. Might not need it often, but sometimes I do.

Another thing I&#039;m missing: If I use Expression media to write IPTC into a CR2 file (not xmp), most gets read by LR. Not so if I do the same for a 1D .tif file (Older Raw format).

Last thing: (remotely connected): Would be nice to be able to script IPTC keywording: For instance copy the filename into an IPTC field.

Those three are the main reason I still need Expression Media alongside LR2.</description>
		<content:encoded><![CDATA[<p>One thing I am missing in LR2 is a &#8220;find missing folders&#8221; and/or &#8220;find missing files.</p>
<p>Now I have to (slowly, since I need to wait for the screen refresh) scroll through 15k+ images to see whether or not some are missing. Might not need it often, but sometimes I do.</p>
<p>Another thing I&#8217;m missing: If I use Expression media to write IPTC into a CR2 file (not xmp), most gets read by LR. Not so if I do the same for a 1D .tif file (Older Raw format).</p>
<p>Last thing: (remotely connected): Would be nice to be able to script IPTC keywording: For instance copy the filename into an IPTC field.</p>
<p>Those three are the main reason I still need Expression Media alongside LR2.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck Clifton</title>
		<link>http://blog.ericscouten.com/2009/09/lightroom-2-technique-how-i-organize-my-catalog-and-why-2009-edition/#comment-5571</link>
		<dc:creator>Chuck Clifton</dc:creator>
		<pubDate>Sun, 31 Jan 2010 03:09:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=349#comment-5571</guid>
		<description>Ok, I got #2 solved.  It&#039;s kinda counter-intuitive because you open up the dialog box where you select the files you want to recognize and they are all greyed out and it wants you to select but you can&#039;t highlight them so you just ckick SELECT and it did take them.
As to #1, maybe I could delete all the -2s as when I open the FOLDERS in LR, it shows duplicates of each photo.  Is there a way to do a DELETE ALL *.JPEG-2?  I don&#039;t want to have to go through and do over 5000 manually.  Or should I delete them all and re-import them all as DNGs?  That may be the best solution.
Chuck</description>
		<content:encoded><![CDATA[<p>Ok, I got #2 solved.  It&#8217;s kinda counter-intuitive because you open up the dialog box where you select the files you want to recognize and they are all greyed out and it wants you to select but you can&#8217;t highlight them so you just ckick SELECT and it did take them.<br />
As to #1, maybe I could delete all the -2s as when I open the FOLDERS in LR, it shows duplicates of each photo.  Is there a way to do a DELETE ALL *.JPEG-2?  I don&#8217;t want to have to go through and do over 5000 manually.  Or should I delete them all and re-import them all as DNGs?  That may be the best solution.<br />
Chuck</p>
]]></content:encoded>
	</item>
</channel>
</rss>
