P: Allow smart collections to reference other smart collections or library filter presets

"Why not make each type of Collection (Smart and "non-Smart") a Collection Set itself? (which can contain as many "Child"-Collections as you want)"

Like Timothy Spear (below), I also use Smart Collections to control the publishing of my photos to multiple online destinations and multiple "in house" destinations - ie multiple publish services. This "most simple" solution is not flexible enough for my needs and in my view and experience (as a system and database designer) should not need this level simplification to aid implementation,

feature request.
I have common settings I use for multiple smart collections used in the catalog, in multiple publishing services. As such, I would like the ability to create a "master smart collection" which any conditions are automatically added to any smart collection which depends on it.
For example, items I want to publish have two stars and cannot have the color red. I use this in about five publish services. It would be nice to not repeat these ever time.

Tim

It would be great if we could make one smart collection depend on another.

For example:

Smart Collection A contains all photos with a certain tag.

Smart Collection B filters RAW-Files and, being a "child collection" to Smart Collection A, only shows those from Smart Collection A.

So if I change the criteria of Smart Collection A, Smart Collection B automatically changes to the corresponding content.

This is a feature I really miss at the moment. Most simple solution: Why not make each type of Collection (Smart and "non-Smart") a Collection Set itself? (which can contain as many "Child"-Collections as you want)

This topic should be merged into:

http://feedback.photoshop.com/photosh...

"Personally, I would have preferred if Adobe made the product better, and continued to offer it at the same price, instead of so few improvements, at a reduced price."

Agreed.

"I should not have to resort to a plugin for what I see is fairly basic database functionality on what is billed as a DAM product."

Agreed.

Personally, I would have preferred if Adobe made the product better, and continued to offer it at the same price, instead of so few improvements, at a reduced price. I guess a large percent of Lightroom users are not very demanding...

Thanks John and Rob, I’ll take a serious look at your plugins.

I guess like LR3, with LR 4 I am somewhat underwhelmed by the list of available fields to filter on, or smart collect on – I know LR has a real database under the bonnet and this stuff should be bread and butter stuff, low lying fruit or many other flavours of such expressions.

Inheritance on smart collections would create some pretty neat flexibility. The ability of an LR 4 smart photo set / gallery to use “Publish Collection” as part of its criteria is frustratingly close to doing the job ... but alas, this does not include smart published collections just non smart ones! Why, oh why could they not have included Publish Smart Collection as a field as well?

No offence to anyone and you guys do fantastic stuff, but I should not have to resort to a plugin for what I see is fairly basic database functionality on what is billed as a DAM product. But credit to you both for wallpapering over some serious shortcomings of the product.

Alan.

Also consider CollectionAgent - it supports collection synchronization, duplication, ...

http://www.robcole.com/Rob/ProductsAn...

The Any Filter plugin provides the ability to define a saved filter that references other saved filters and smart collections. Not quite as convenient as having it builtin to smart collections, but it may get the job done for you depending on your needs.