Filter Preset Unique for each Catalog?

Report · Aug 21, 2023

I have two catalogs, one that is synced and one is not. In both catalogs, the keyword hierarchy are the same. I have created Filter Presets that are based some keyword; but no matter how double, tripple check the keywords despite they are all the same, I cannot get the Filter Preset works across the two catalogs... Then I did a more in depth digging, seems like the filter preset is unique for each catalog? Below is what I found.

I have two catalogs, let's call it Cat_A & Cat_B, they both have the same Keywords (100% sure, I will get into that later). I create a Filter Preset in Cat_A, let's call it FilterPreset_A, then I open Cat_B, I can see the FilterPreset_A that I created in Cat_A (so they are not saving presets with the catalog). When I select the FilterPreset_A in Cat_B, it returns no photo. Like wise, if I create a Filter Preset in Cat_B, let's call it FilterPreset_B, I can see it in Cat_A, but return no photos when I select the FilterPreset_B in Cat_A.

I have tested this with a hard-to-type-wrong keyword: "Test" (without quotation). I then open the .lrtemplate file for the two Filter template. Seems apart from the keyword, the reset are represeted by true / false or number / text; for the keyword, it's represented by a number (232944 and 507712 in below).... and despite the two catalog has the same keyword "Test" (at the outermost hierarchy), they have different number representing it... instead of using the actualy Keyword... Why is it like that? No idea.... ; but for now.... that means I have to create two Filter Template for each catalog, although, I prefer creating only one...

For non-keyword related filter, it works in both catalog. Is there any reason that Keywords are represented by numers instead of the text? Is that because of the hierarchy of keywords that makes this impossible to use text base to store the template?

Report · Aug 22, 2023

The numbers stored in the filter presets are the internal unique identifiers of the keywords in the catalog database. I'm sure that when the filter presets were first implemented, the developer thought that using the unique ids was simple and expedient. But your use case shows that it would have been better to store the fully qualified names of the keywords in the presets, e.g. "People>John's Family>John Ellis".

You could post a feature request about this:

https://community.adobe.com/t5/lightroom-classic-ideas/how-do-i-write-a-feature-request/idi-p/123863...

though I'm personally skeptical Adobe would prioritize any request having to do with filters and smart collections at this late date in Lightroom Classic's life cycle.