I posted this before, but with over 200 posts in this thread it is hard to find, so here it is again. the crux of the post is a way for Adobe to do this without putting hierarchical KW's in LR/Cloud. At this time, I am considering the official "reason" for not fixing this as pure BS. This is no where as complicated as AI in masking or super noise reduction and they were able to do that. Adobe says that "a hierarchical schema is not compatible for various workflows". I don't buy it, and won't buy it unless someone from Adobe articulates exactly what those incompatibilities are and why various suggested solutions (like mine) won't work. Here's the idea.... Cloud / Classic keyword Sync Requested 2017 Fully Sync keywords between Classic and Cloudy. Add “sync” options to add/edit keyword screens While keeping the constraint that LR Classic uses hierarchical KW's and LR Cloudy uses a linear (flat) KW structure, this problem can be solved. There are, of course, some technical aspects but the main rationale I've heard so far for not doing this is the logical problem of how to map a hierarchical structure to a linear structure. One solution is to convert LR Cloudy to a hierarchical structure but putting that aside, here is one possible solution to that problem: In LR Classic, add 3 new check boxes in the create/edit keyword dialog for, "Sync this KW with LR Cloud", "Sync Containing KW's with LR Cloud", and "Sync Synonyms with LR Cloud (synonyms would become regular KW's in LR Cloud) When a user ticks any of these new boxes, LR Classic would check to assure that it is not redundant. For example, if you already ticked KW "Red" under "Flowers", and now you are trying to tick keyword "Red" under "Cars": it would reject the request as a duplicate. By doing this, it will enforce a one to one correspondence between ticked KW's in LR Classic and KW's in LR Cloud - thus negating Adobe's excuse for not syncing KW's If a user defined KW is added to an image in LR Cloudy it could map to either no existing KW's in LR Classic or at the most to one "ticked" KW in LR Classic. In the former case, LR Classic would create the new KW at the root level of the Hierarchy with "Sync this KW with LR Cloudy" ticked. If there already was one, it would just add check the tick box. In the later case there could be only 1 ticked LR Classic Keyword with that name that would be affected. If you add KW in Classic or tick one of these new boxes on an exisitng KW, after assuring that word is not similarly ticked in any other KW, the KW would be sent and added to LR/Cloud. THIS CAN BE DONE if there is a will to do so at Adobe and the more people who speak up for having KW's sync between the ecosystems, the more it will push Adobe to re-consider this.
... View more