<?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: Smart Collections and Worklists</title>
	<atom:link href="http://ericscouten.com/2008/08/lightroom-2-technique-smart-collections-and-worklists/feed/" rel="self" type="application/rss+xml" />
	<link>http://ericscouten.com/2008/08/lightroom-2-technique-smart-collections-and-worklists/</link>
	<description>The photography, travel, and technology blog of Eric Scouten</description>
	<lastBuildDate>Thu, 26 Jan 2012 17:07:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Steven Grimm</title>
		<link>http://ericscouten.com/2008/08/lightroom-2-technique-smart-collections-and-worklists/#comment-5646</link>
		<dc:creator>Steven Grimm</dc:creator>
		<pubDate>Thu, 01 Dec 2011 00:37:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=82#comment-5646</guid>
		<description>Thanks for this post -- I&#039;d been using keywords for this and finding it a little cumbersome. This seems like it&#039;ll be better and it seems like the whole thing still applies as-is to LR3.

One thought on collection naming: In my existing (keyword-based) smart collections I use numeric prefixes on the collection names to keep them in a particular order in the UI. This would probably be a reasonable thing to use for the smart collections too. That is, if you have a collection named something like, &quot;031 People I know - Reviewed&quot; you can key on &quot;031&quot; in the smart collection and be fairly well assured you&#039;ll never run into problems with partial matches or the like.

Of course, putting numbers in the name doesn&#039;t imply you have to go through the collections in any particular order in your workflow; it&#039;s just really easy to make sure numbers are unique since any duplicates will sort right next to each other in the collections list.</description>
		<content:encoded><![CDATA[<p>Thanks for this post &#8212; I&#8217;d been using keywords for this and finding it a little cumbersome. This seems like it&#8217;ll be better and it seems like the whole thing still applies as-is to LR3.</p>
<p>One thought on collection naming: In my existing (keyword-based) smart collections I use numeric prefixes on the collection names to keep them in a particular order in the UI. This would probably be a reasonable thing to use for the smart collections too. That is, if you have a collection named something like, &#8220;031 People I know &#8211; Reviewed&#8221; you can key on &#8220;031&#8243; in the smart collection and be fairly well assured you&#8217;ll never run into problems with partial matches or the like.</p>
<p>Of course, putting numbers in the name doesn&#8217;t imply you have to go through the collections in any particular order in your workflow; it&#8217;s just really easy to make sure numbers are unique since any duplicates will sort right next to each other in the collections list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Organising a Lightroom catalog &#124; Timothy Armes' Blog</title>
		<link>http://ericscouten.com/2008/08/lightroom-2-technique-smart-collections-and-worklists/#comment-5609</link>
		<dc:creator>Organising a Lightroom catalog &#124; Timothy Armes' Blog</dc:creator>
		<pubDate>Wed, 22 Sep 2010 15:20:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=82#comment-5609</guid>
		<description>[...] to keep track of which images still need sorting and keywording. I highly recommend reading his blog post on the [...]</description>
		<content:encoded><![CDATA[<p>[...] to keep track of which images still need sorting and keywording. I highly recommend reading his blog post on the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://ericscouten.com/2008/08/lightroom-2-technique-smart-collections-and-worklists/#comment-5596</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Tue, 03 Aug 2010 04:52:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=82#comment-5596</guid>
		<description>Hi Lisbeth, it&#039;s been a while since I&#039;ve looked at the exact details for smart collection searches, but you might try the &quot;contains all&quot; or &quot;contains words&quot; options.</description>
		<content:encoded><![CDATA[<p>Hi Lisbeth, it&#8217;s been a while since I&#8217;ve looked at the exact details for smart collection searches, but you might try the &#8220;contains all&#8221; or &#8220;contains words&#8221; options.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisbeth</title>
		<link>http://ericscouten.com/2008/08/lightroom-2-technique-smart-collections-and-worklists/#comment-5595</link>
		<dc:creator>Lisbeth</dc:creator>
		<pubDate>Sun, 01 Aug 2010 08:46:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=82#comment-5595</guid>
		<description>Hi Eric
How do I create a smart collection with pictures of Snowwhite  if I also have pictures of snow? The problem is, that when I create a smart collection searching for the keyword Snowwhite it includes all pictures with the keyword &#039;snow&#039;. And if I say that it shouldn&#039;t include &#039;snow&#039; it excludes all pictures with SNOWwhite and leaves nothing back!!</description>
		<content:encoded><![CDATA[<p>Hi Eric<br />
How do I create a smart collection with pictures of Snowwhite  if I also have pictures of snow? The problem is, that when I create a smart collection searching for the keyword Snowwhite it includes all pictures with the keyword &#8216;snow&#8217;. And if I say that it shouldn&#8217;t include &#8216;snow&#8217; it excludes all pictures with SNOWwhite and leaves nothing back!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lowflyinghawk</title>
		<link>http://ericscouten.com/2008/08/lightroom-2-technique-smart-collections-and-worklists/#comment-5552</link>
		<dc:creator>lowflyinghawk</dc:creator>
		<pubDate>Sun, 06 Dec 2009 22:43:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=82#comment-5552</guid>
		<description>I seldom use the word &quot;awesome&quot;, but I must say it:  this technique is freaking awesome!  I have 35,000 family pics taken over around 10 years that I recently imported into LR.  unlike PSE6, LR didn&#039;t fall down and die from the load, but organizing them beyond a few coarse-grained collections seemed just about insurmountable until I read your article.  I got set up and classified the first 3500 or so in a &quot;family&quot; hierarchy in a couple of hours.  thanks to the &quot;reviewed&quot; and &quot;to review&quot; setup I can stop and restart again whenever I&#039;m in the mood.  I&#039;ll say it again:  awesome!</description>
		<content:encoded><![CDATA[<p>I seldom use the word &#8220;awesome&#8221;, but I must say it:  this technique is freaking awesome!  I have 35,000 family pics taken over around 10 years that I recently imported into LR.  unlike PSE6, LR didn&#8217;t fall down and die from the load, but organizing them beyond a few coarse-grained collections seemed just about insurmountable until I read your article.  I got set up and classified the first 3500 or so in a &#8220;family&#8221; hierarchy in a couple of hours.  thanks to the &#8220;reviewed&#8221; and &#8220;to review&#8221; setup I can stop and restart again whenever I&#8217;m in the mood.  I&#8217;ll say it again:  awesome!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://ericscouten.com/2008/08/lightroom-2-technique-smart-collections-and-worklists/#comment-5544</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Mon, 23 Nov 2009 19:00:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=82#comment-5544</guid>
		<description>Perhaps I need to clarify the article. You can&#039;t directly add photos to a smart collection, so the &lt;b&gt;B&lt;/b&gt; key is invalid in that context. What I am doing is to use a standard collection and a smart collection as a pair. The smart collection is defined as those photos that are &lt;i&gt;not&lt;/i&gt; in the standard collection, and I use the &quot;set as target collection&quot; on the &lt;i&gt;standard&lt;/i&gt; collection. In that case, using the B key has the effect of adding the photo to the standard collection and causing that photo to no longer match the criteria for the smart collection.</description>
		<content:encoded><![CDATA[<p>Perhaps I need to clarify the article. You can&#8217;t directly add photos to a smart collection, so the <b>B</b> key is invalid in that context. What I am doing is to use a standard collection and a smart collection as a pair. The smart collection is defined as those photos that are <i>not</i> in the standard collection, and I use the &#8220;set as target collection&#8221; on the <i>standard</i> collection. In that case, using the B key has the effect of adding the photo to the standard collection and causing that photo to no longer match the criteria for the smart collection.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Endre Grüner Ofstad</title>
		<link>http://ericscouten.com/2008/08/lightroom-2-technique-smart-collections-and-worklists/#comment-5543</link>
		<dc:creator>Endre Grüner Ofstad</dc:creator>
		<pubDate>Mon, 23 Nov 2009 18:57:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=82#comment-5543</guid>
		<description>Hi, great system I have just one problem: I miss the &quot;set as target collection&quot; function with Smart Collection. That alternative only works with regular collection. What seems to be the problem?</description>
		<content:encoded><![CDATA[<p>Hi, great system I have just one problem: I miss the &#8220;set as target collection&#8221; function with Smart Collection. That alternative only works with regular collection. What seems to be the problem?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Englebright</title>
		<link>http://ericscouten.com/2008/08/lightroom-2-technique-smart-collections-and-worklists/#comment-5408</link>
		<dc:creator>Robert Englebright</dc:creator>
		<pubDate>Mon, 21 Sep 2009 16:46:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=82#comment-5408</guid>
		<description>I feel like I have followed all the directions correctly, but I am missing how the photos are removed from the Smart Collection after I have done the keywording and pressed the &quot;b&quot; key.  After I press the &quot;b&quot; the photos migrate to the target collection but stay in the Smart Collection.  I was under the impression from your directions that the photo is removed from the Smart Collection immediately once I press the &quot;b&quot; key.  Am I supposed to keyword &quot;flowers»reviewed&quot; after I have pressed the &quot;b&quot; key, and this is when the photos migrate to the target collection?</description>
		<content:encoded><![CDATA[<p>I feel like I have followed all the directions correctly, but I am missing how the photos are removed from the Smart Collection after I have done the keywording and pressed the &#8220;b&#8221; key.  After I press the &#8220;b&#8221; the photos migrate to the target collection but stay in the Smart Collection.  I was under the impression from your directions that the photo is removed from the Smart Collection immediately once I press the &#8220;b&#8221; key.  Am I supposed to keyword &#8220;flowers»reviewed&#8221; after I have pressed the &#8220;b&#8221; key, and this is when the photos migrate to the target collection?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Beedon</title>
		<link>http://ericscouten.com/2008/08/lightroom-2-technique-smart-collections-and-worklists/#comment-5044</link>
		<dc:creator>Dave Beedon</dc:creator>
		<pubDate>Thu, 26 Mar 2009 06:16:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=82#comment-5044</guid>
		<description>Eric,
This information will be of great value to me when I start using Lightroom (I ordered it yesterday). The idea of using keywords and collections excites me. From what I have learned so far, Lightroom 2.0 will be a dramatic improvement in capability over my present &quot;dark ages&quot; photo management system. Thank you very much for sharing your system of using keywords and collections!</description>
		<content:encoded><![CDATA[<p>Eric,<br />
This information will be of great value to me when I start using Lightroom (I ordered it yesterday). The idea of using keywords and collections excites me. From what I have learned so far, Lightroom 2.0 will be a dramatic improvement in capability over my present &#8220;dark ages&#8221; photo management system. Thank you very much for sharing your system of using keywords and collections!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Winston Mitchell</title>
		<link>http://ericscouten.com/2008/08/lightroom-2-technique-smart-collections-and-worklists/#comment-4594</link>
		<dc:creator>Winston Mitchell</dc:creator>
		<pubDate>Wed, 20 Aug 2008 18:15:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericscouten.com/?p=82#comment-4594</guid>
		<description>Eric, I have spent a long time thinking about this problem. I have discovered my real problem with this new method. This method treats a file&#039;s location as data without any record of how it got there. It cannot easily be reconstructed. Also, this &quot;data&quot; can be altered with no visible trace. For an aging dyslexic, such as myself, this is unacceptable.

I thought about a similar method where I would use the painter to apply the appropriate worklist keyword and rejected it for the same reason I can&#039;t use Auto Sync.

What I have settled on is creating a &quot;WorkList&quot; keyword set. This seems to work pretty well. It is still applied via kestroke with the added benefit of instananeous visible feedback and a simpler collection structure.

Thanks for listening.</description>
		<content:encoded><![CDATA[<p>Eric, I have spent a long time thinking about this problem. I have discovered my real problem with this new method. This method treats a file&#8217;s location as data without any record of how it got there. It cannot easily be reconstructed. Also, this &#8220;data&#8221; can be altered with no visible trace. For an aging dyslexic, such as myself, this is unacceptable.</p>
<p>I thought about a similar method where I would use the painter to apply the appropriate worklist keyword and rejected it for the same reason I can&#8217;t use Auto Sync.</p>
<p>What I have settled on is creating a &#8220;WorkList&#8221; keyword set. This seems to work pretty well. It is still applied via kestroke with the added benefit of instananeous visible feedback and a simpler collection structure.</p>
<p>Thanks for listening.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

