Skip to main content
mikecox_
Inspiring
April 27, 2024
Answered

Collection sort error

  • April 27, 2024
  • 6 replies
  • 569 views

 

Don't understand why I get this unexpected result from this Smart collection.

This is just one of the many unexpected results I'm getting.

 

This topic is closed to new replies. Start a new post to keep the conversation going.
Correct answer richardplondon

An image can be 'deemed to have' a certain keyword (for purposes of searching or filtering, also exporting) even without that keyword being explicitly and directly assigned, in several circumstances:

 

  • A keyword that it does have assigned possesses this other keyword as a synonym
  • A keyword that it does have assigned possesses this other keyword as a parent
  • If "contains" is used rather than "contains words", and some longer keyword that is assigned, or a synonym or a parent of that, includes this same string of characters within it.

 

Thus, if I've assigned a keyword "yellow" and add a synonym "amber" to that, a search on "amber" will find that photo (and also it will include in export) even though it does not have any "amber" keyword directly assigned, and even though I did not search on "yellow". This despite "amber" not even showing in the keywords list.

Similarly for parent keywords. There are keyword options on whether any parents should, or should not, auto-include for export. But they operate regardless "as if assigned" (implicitly) for searching and filtering. Dragging the child keyword out of that nesting, would cease this relationship with the former parent keyword - unless that keyword was also explicitly assigned in its own right.

6 replies

richardplondonCommunity ExpertCorrect answer
Community Expert
April 28, 2024

An image can be 'deemed to have' a certain keyword (for purposes of searching or filtering, also exporting) even without that keyword being explicitly and directly assigned, in several circumstances:

 

  • A keyword that it does have assigned possesses this other keyword as a synonym
  • A keyword that it does have assigned possesses this other keyword as a parent
  • If "contains" is used rather than "contains words", and some longer keyword that is assigned, or a synonym or a parent of that, includes this same string of characters within it.

 

Thus, if I've assigned a keyword "yellow" and add a synonym "amber" to that, a search on "amber" will find that photo (and also it will include in export) even though it does not have any "amber" keyword directly assigned, and even though I did not search on "yellow". This despite "amber" not even showing in the keywords list.

Similarly for parent keywords. There are keyword options on whether any parents should, or should not, auto-include for export. But they operate regardless "as if assigned" (implicitly) for searching and filtering. Dragging the child keyword out of that nesting, would cease this relationship with the former parent keyword - unless that keyword was also explicitly assigned in its own right.

mikecox_
mikecox_Author
Inspiring
April 28, 2024

Thanks for that quick and very helpful response.

Using Win 11
Ian Lyons
Community Expert
Community Expert
April 28, 2024

Your screenshot and reference to collections indicates that you're using Lightroom Classic. Therefore, I've moved the thread to the correct forum.

mikecox_
mikecox_Author
Inspiring
April 28, 2024

Thanks, I'll be more careful about that in future.

Using Win 11
Ian Lyons
Community Expert
Community Expert
April 28, 2024

It happens quite often and is more Adobe's fault than yours.

mikecox_
mikecox_Author
Inspiring
April 27, 2024

Does it have something to do with Keyword subfolders?

Using Win 11