Interestingly, I had to do that to get this to work. My goal was to create a situation where I had an orphaned hierarchical keyword in my file. If I left that setting on, to write hierarchical keywords, when I deleted the flat keyword, the hierarchical keyword got deleted also. If I changed that setting, I could delete the flat keyword without deleting the hierarchical one.vlad wrote: tstoddard wrote:
Then I changed my preferences to NOT write hierarchical keywords but still to read hierarchical keywords.
Why did you change your preferences to NOT write hierarchical keywords? Did that make any difference? (Anyway, I somehow doubt that Stephen turned off the writing of hierarchical keywords.)
I doubt that Stephen made the same changes I did, also, but he has admitted to experimenting quite a bit so it is possible that he had changed settings after some of these keywords and labels were created.
You're right about the Keyword processing, it was set to Merge Catalog labels with Keywords. I did change that but wasn't sure it made a difference. With my workflow, I have never noticed a difference in any behavior when changing that setting but for this example I didn't want PSU to mess with the keywords so I changed it.vlad wrote:How did you configure Keyword processing in the global preferences for writing? My guess is that you specified: "Merge Catalog labels with Keywords". If you had "Replace keywords with Catalog labels" (my preference), I expect that the keyword would have been removed. (Furthermore: why would there be any difference between manual and automatic saving of metadata, regardless of the write preference?)
I had to switch to manual saving of metadata because if I didn't, when I changed the metadata setting in the label to not write a keyword, the keyword was removed immediately. What I did was to change that setting and then delete the label before saving metadata to the file. That way, the label was unassigned from the file but the keywords remained.
I created my test label under Miscellaneous to begin with so the hierarchical keyword was "Miscellaneous|TestLabel". Since Stephen's issue indicated his label was in that category, I figured it was an appropriate place to put it. I assume that his labels are in there because he either imported images with flat keywords in them and PSU created labels in Miscellaneous automatically or he entered the keywords using the details panel and when he did he was only entering them in the dc:subject field so PSU would have created labels in the Miscellaneous category to correspond with those keywords.vlad wrote:Sure, but the labels created from hierarchical info should not be created under Miscellaneous. Was your label created under that category, Tom?
Like I said in my post, "it wasn't easy". I had to do some nonsensical things in order to make this happen so I doubt that Stephen did exactly what I did but it did prove to me that it is possible to have an orphaned hierarchical keyword written to a file that will result in a label and keyword being created or recreated automatically when metadata is written to a file.