P: Add an option to always export complete keyword hierarchy

I have the same problem with export/import for HDR Efex, Photomatix, etc. editing. It's driving me nuts. How about also having a feature to simply LOCK the keyword hierarchy, so nothing can modify the keyword structure, unless you specifically authorize it. A blunt tool, but my first instinct with a problem is to put the solution (even if temporary) as near to the damage as possible, to prevent outflanking manouevers by the software.

I had this problem too, I always blamed the 3rd party software that must have broken the hierarchy. just realized it was LR actually doing this.

if I have parent keywords that are used only to categorize other keywords (like the ABCs or a keyword called "technique") that house other keywords using the include on export option isn't really an option.

has anyone found a workaround for this by now? (Lightroom 4.1)

Shai

May I chime in? Thanks to Louie for pointing me to this forum.
I am experiencing the keyword export/reimport annoyance right now when using NIK software combined with Lightroom.
In LR I start with a picture keyworded with hierarchical keywords and I edit it in Viveza. This creates a TIF copy of my original RAW picture in Lightroom, which is then edited in Viveza and reimported into Lightroom. During the automatic reimport process new keywords are created, old ones get lost, because during the export the hierarchical keyword structure gets destroyed. it produces a total mess in LR.
If anyone is interested in seing the step-by-step process, I have documented it in the Ligthroom forum here:
http://www.lightroomforums.net/showth...

I concurr with everyone who asks that the keyword issue must be fixed.

This continues to be a problem for anyone that wants or needs to use Export to create derivative files and import them back into Lightroom to be managed.

The practical effect is that Lightroom without asking creates a new hierarchical keyword. It is a valid use case for some one to want to do this. It is also a valid use case for someone to want to remove the "not for export" terms in the hierarchy. There is absolutely no reason that I can think of for not allowing the option for either.

We know that the old way worked by exporting the old hierarchy intact. We know that the new code works by removing not for export elements and reformation hierarchy. So how difficult is it you put both pieces of code in and tie the execution to a conditional check box in the export dialog????????

I continue to be terribly frustrated with the fact that virtually nothing has been done to improve the keyword features and management since before LR3 was released. This happens to be one of the few changes to how keywords are handled and it as make using keywords harder not easier.

-louie

I forgot to tell that I don't want the synonyms at the exported pics for this special client. They mess up my clients keyword list, but I need them myself. It used to work perfectly and was one of the reasons to choose LightRoom.

I used this option (checked) to send keyworded pics to a client, who imported them and then exported them with this option unchecked, so his keyword list would not be a mess afterwards.

Now I'm back to the LR verson before 3.5 , really annoying. I don't know nor understand if Adobe is going the change this problem for me. I'm forced to work with old versions, which is no good and very unprofessional.

Elise Swart

ExportMaster assures keywords of exported photos are same as source photo.

Somebody should write an export filter to do this for the mean time.

I could knock this out fairly quickly (as could anyone with plugin programming experience (e.g. Jeff Stephenson) who has learned to use the elare plugin generator which has a switch to make a plugin that includes a skeletal export filter), but would more than a few lone adventurers actually use it? (my experience has been that many plugin-phobes would rather do without than use a plugin solution, or would just never find out that it exists...)

Note: the keyword handling exposed by the SDK is not as straightforward as you might like, but there are examples that could be harvested... - let me know if you need help...

Rob

Prior to v3.5, when exporting an image and checking the “Write Keywords As Lightroom Hierarchy” option, a keyword always included the parent keywords as well as the structure. Starting with v3.5, this is only the case if each of the parent keywords are saved with the “Include on Export” properly selected.

Although the new behavior may be technically more correct based on the option descriptions, it creates what LR believes to be new keywords when importing certain exported images back into the catalog, even when re-importing immediately after export using the re-import option built into the export routine.

If this change is a bug, I would like to ask that it be fixed back to the prior behavior. If this change is a feature correction, I would like to ask that the feature be expanded to include an “Include all Parent Keywords in Hierarchy” sub-option to allow those of us that are accustomed to the prior behavior to be able to return.

I know I could edit each keyword that does not have the “Include on Export” option checked; however, many exports I perform do not involve selecting the “Write Keywords As Lightroom Hierarchy” option and in those cases I don’t really want the parent keywords exported which is why they are currently set up in that manner.

This idea/bug is a follow up to the discussion at: http://feedback.photoshop.com/photosh...

Jeff

Rob to your point Adobe has apparently taken the position that Export by definition is "only" used to create images for external consumption. It is, I believe, too limited a point of view. There are many valid use cases where you do want to keep all your metadata which is now not possible.