iptc4xmpExt:Event is now emtpy in V3

[bimo]

V3-List of changes 46. During a sync, the Iptc4xmpExt:Event will be written with the first found catalog label
name from the Events category

My Events catalog Labels are structured as "Events>vacation trip>2010 USA" and the like.

"Vacation Trip" is defined as "generate keyword", but no link to iptc4xmpExt:Event has been established.
For "2010 USA" no keyword is generated, but it's linked to iptc4xmpExt:Event.

Before v3, I had "vacation trip" in the keywords section and found "2010 USA" as Name of the Event in iptc4xmpExt:Event.

Now, in v3, I still find "vacation trip" in the keywords, but iptc4xmpExt:Event is empty.

What is wrong with the definitions or am I misunderstanding the concept?

Michael

[Hert]

In V3 the iptc4xmpExt:Event is automatically filled with the name of a catalog label that you have assigned in the designated "Events" category. If "2010 USA" is a private catalog label then it will also not fill in the iptc4xmpExt:Event.

[bimo]

To better understand what is wrong with my kind of labeling these are the appropriate details:

events.JPG (13.68 KiB) Viewed 4398 times

vacationtrip.JPG (33.52 KiB) Viewed 4398 times

2010 USA.JPG (36.53 KiB) Viewed 4398 times

IMHO it's not private and I can't figer out, why it's no longer written to iptc4xmpExt:Event.

I'm very much looking forward to your answer and help, Hert.

Michael

[Hert]

Michael, the reason is that you have this catalog label defined as "Kein Schlusselwort fur dieses..." (sorry for omitting the umlauts buts I don't have those available on my keyboard). That setting makes that this catalog label is ignored for the "event" mapping.
But...you do have a manual XMP mapping to Iptc4xmpExt:event. I've looked it up and the XMP mapping is processed *before* the automated event category mapping. And so your manual mapping is emptied afterwards when PSU finds that there's no (applicable) Event label. That is incorrect. The mapual XMP mapping should take place *after* the automated event mapping. I've corrected that for build 2056 and with that update your issue will be resolved. Until then I'm afraid I have no other workaround but to enable the keyword.

[bimo]

Hert, thank you very much for your fast response and bugfix. It's no problem for me to wait for the fix to be published because in this case no changes have to be done in this category.

Michael

[bimo]

Hert, works like a charm now. THX again.

Michael