• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.
  • Dark mode now has a single preference for the whole site! It's a simple toggle switch in the bottom right-hand corner of any page. As it uses a cookie to store your preference, you may need to dismiss the cookie banner before you can see it. Any problems, please let us know!

Virtual tags?

Status
Not open for further replies.
Joined
Aug 31, 2022
Messages
5
Lightroom Version Number
10.4
Operating System
  1. Windows 10
Is it possible to create virtual tags?

For example, I would like to create a tag "field flowers" that means "flower AND plant BUT NOT garden", that automatically becomes checked for a photo where its tags meet this condition.

Stupid example, but it's just to illustrate what a virtual tag might mean. It's basically a smart collection, but not a collection. A virtual tag would be a tag that might appear among the tags or in a separate section, and is (obviously) readonly. It would need to be filterable as well.

Can I do something like that?
 
What you are describing is a smart Collection based upon keywords. The concept of "virtual tag" or "virtual keyword" does not exist in Lightroom. So a Smart Collection is the only way to achieve what you want in Lightroom Classic.

And "keyword" is the correct terminology to use inside the Lightroom environment. Keyword is an ITPC Field. A tag in EXIF terminology is an identifier for various metadata Fields including The ITPC Keyword. When talking about image files, we use the term Keyword to avoid confusion.
 
My suggestion would be to turn this around and instead of defining a solution with ‘virtual tags’ focus on how you can find “flower AND plant BUT NOT garden". The reason being is that you will develop far to many tags as you want to classify effectively searches.

To that end I’d suggest looking at John plug in that uses Google AI to keyword pictures. He also has plugs to help in searches. https://johnrellis.com/lightroom/an...30.1999216272.1661950698-969619740.1661950698

Your desire to find something is based on a tool being able to parse and recognize objects in a photo. These are getting better but still have a ways to go IMHo
 
If you put "Flower" under "Plant" in the Keyword (hierarchy list, but have "Garden" at the same level as "plant" then Plant will automatically be considered as an associated keyword for any image that has the Flower keyword. However, the Garden keyword will be independent of the other two and can be associated witht he same image or not as you choose.

If you export an image that has the Flower keyword, depending on your settings in the Flower and the Plant keywords you can choose wether or not Plant will in included in the exported keywords (tags). Again, Garden would be independent and would export if it was also assigned to the image.
 
What you are describing is a smart Collection based upon keywords. The concept of "virtual tag" or "virtual keyword" does not exist in Lightroom. So a Smart Collection is the only way to achieve what you want in Lightroom Classic.

And "keyword" is the correct terminology to use inside the Lightroom environment. Keyword is an ITPC Field. A tag in EXIF terminology is an identifier for various metadata Fields including The ITPC Keyword. When talking about image files, we use the term Keyword to avoid confusion.
Ok, keywords then. Most applications call them tags. Whatever floats your boat :)
Collections have the great disadvantage of being unable to "apply" it to a folder, like you can by filtering on a keyword. On top of that, yes, I know you can extend the conditions in a smart collection with "Folder" but I've never found out what exactly I am expected to put there. Nothing useful seems to be working, afaict.
My suggestion would be to turn this around and instead of defining a solution with ‘virtual tags’ focus on how you can find “flower AND plant BUT NOT garden". The reason being is that you will develop far to many tags as you want to classify effectively searches.

To that end I’d suggest looking at John plug in that uses Google AI to keyword pictures. He also has plugs to help in searches. https://johnrellis.com/lightroom/an...30.1999216272.1661950698-969619740.1661950698

Your desire to find something is based on a tool being able to parse and recognize objects in a photo. These are getting better but still have a ways to go IMHo
You're assuming I have added these keywords in the first place ;)
I feel you're suggesting I should design my keywords to aid the tool, but I'd rather have the other way round. The tool should assist me instead.
If you put "Flower" under "Plant" in the Keyword (hierarchy list, but have "Garden" at the same level as "plant" then Plant will automatically be considered as an associated keyword for any image that has the Flower keyword. However, the Garden keyword will be independent of the other two and can be associated witht he same image or not as you choose.

If you export an image that has the Flower keyword, depending on your settings in the Flower and the Plant keywords you can choose wether or not Plant will in included in the exported keywords (tags). Again, Garden would be independent and would export if it was also assigned to the image.
The problem with nested keywords is that Lightroom treats them very unpredictably in searches. In filtering it's nearly alright, except that you can't make a "NOT keyword" filter. So only positive keywords are possible. In smart collections, filtering by keywords works completely weird. Something like Plant->Fower cannot be searched for. Instead you would have to search for "Flower", but there is no way to make it look for Flower specifically under Plant. Which will lead to unexpected behaviour when I also happen to have a Flower keyword under Sculptures that I *don't* want to search for. Even worse, it will happily also return results for Flowering and Cornflower even though that is absolutely not what I've typed in. Believe you me, I tried smart collections with *very* disappointing results - unless, like I said, I re-keyword my pictures for the sole purpose of getting Lightroom to do what I want.

---
Anyway, I digress. I guess the feature I'm looking for, is not possible without re-keywording a lot of pictures, and for new pictures in the future. Or by creating unstable results in smart collections where I can't switch from folder to folder.

I don't know if the Lightroom devs are reading along (if not, they probably should be!) because this keywording debacle has been bothering me not since when I created this topic, but for years now. Looking at the database structure of a catalog, it should be fairly easy to create functionality in Lightroom to build ubiqitous and predictable keyword filtering, applicable with the foundational operators AND, OR, NOT and XOR. That would help a bunch.
 
Last edited:
You can use filters rather than smart collections to achieve what you want. The advantage of a filter is that you can run it on any folder (you can save it as a filter preset). If you want to search for flower AND plant BUT NOT garden, then use the following filter:
Keywords: contains all: flower plant !garden
Note the exclamation point in front of ‘garden’. That is the secret trick. If you add an exclamation point in front of a word, then to Lightroom this means ‘not that word’.
 
The problem with nested keywords is that Lightroom treats them very unpredictably in searches
I think it is very consistent. When you search (i.e. filter) on a keyword, explicitly assigned KW 's and implicitly assigned KW's are looked at. Not sure what you are refering to.

except that you can't make a "NOT keyword" filter.
Not true. Place an exclaimation point (!) in front of a word in your criteria box and it makes it a "not". For example "!garden" would exclude any image that has "Garden" in any implicit or explicit KW associated with the image.
Instead you would have to search for "Flower", but there is no way to make it look for Flower specifically under Plant
You are correct and this would be a problem is you have occurances of "flower" under more than one parent. However, I believe that the "AnyFilter" plugin allows you to do this

Which will lead to unexpected behaviour when I also happen to have a Flower keyword under Sculptures that I *don't* want to search for.
The filter below will return image that have keyword "Flower" as long as they don't also have keyword "Sculpture" (or any children keywords under Sculpture). Note "!" in front of "Sculpture"
1661981032222.png


it will happily also return results for Flowering and Cornflower
Yes it will. However, the AnyFilter plug in allows you to deal with this. You can also use "contains words" which looks at only full words (but is somewhat finiky)

I don't know if the Lightroom devs are reading along (if not, they probably should be!) because this keywording debacle has been bothering me not since when I created this topic, but for years now. Looking at the database structure of a catalog, it should be fairly easy to create functionality in Lightroom to build ubiqitous and predictable keyword filtering, applicable with the foundational operators AND, OR, NOT and XOR. That would help a bunch.
You're correct in that there is plenty of room for imporvement needed in the filter tool, not the least of which is their treating each seperate word in a KW phrase as if it were a keyword in its own right (I'm now putting hyphens between my words in keyword phrases) and then making the synonym the phriase for exporting without the hyphens). However, even given the limitaitons, I think it's somewhat more useful than you claim.
 

Attachments

  • 1661980850544.png
    1661980850544.png
    7.1 KB · Views: 67
You're assuming I have added these keywords in the first place ;)
I feel you're suggesting I should design my keywords to aid the tool, but I'd rather have the other way round. The tool should assist me instead.
I don't think I was clear; sorry.
When I saw “flower AND plant BUT NOT garden" I assumed you expected the objects in the image to be recognized first. That was the reason for suggesting using auto keywording using something like Any Vision. Once the keywords were assigned then you could search them.
 
Status
Not open for further replies.
Back
Top