In another post I finally discovered that PL5 will handle keywords placed in a JPG successfully after my original complaints back in February 2021 in my first PL5 Beta test post!
PL5 will still not detect any real time changes made to the metadata by ExifPro which manages to make those changes without causing the ‘Date last modified’ timestamp to change! Other software does detect in real-time so their detection mechanisms seem to be that bit more sensitive. This particular issue has bugged me from the beginning and still does because of tests where changes simply haven’t been detected successfully by PL5.
However, the good news appeared to be that another fault whereby after a ‘Read from Image’ command successfully imported the ExifPro set metadata into PL5, PL5 would then not be able to make changes to that metadata nor export the JPG!
In the latest release that issue no longer appeared to be a problem so that I could update all the ‘Family’ photos I have been tagging since 2003 - Hooray!
But on checking the images I re-discovered an old issue (I reported about a year ago) and discovered a new one which may well exist in another post (a simple search did not locate it but …).
The problems are:-
The keywords set by ExifPro are placed in the xmp ‘dc’ fields but PL5’s obsession with the hierarchical keys means that it sets the data in the ‘hr’ fields as well! No simple metadata handling software even knows that the ‘hr’ keys exist so any deletions from the keyword data made by those programs will result in no apparent change in PL5.
PL5 appears to have lost my ‘Artist’ data added when ACDSee imported the photos from the SD card!
If a non-‘hr’ aware program deletes the ‘dc’ keywords then PL5 and any other software which is prepared to accept simple ‘hr’ keywords with no ‘dc’ counterpart will also consider that the keywords are still present! Deletion from within PL5 removes both but both should not be there in the first place!!
PL5 should not propagate simple ‘dc’ only keys to the ‘hr’ fields, it may well break the guidelines but in my simplistic brain it is simply wrong and creates way more problems than it ever solves - so why do it???
The loss of the ‘Artist’ field is …???
Hope this post is short enough and too the point.
PS Now I need to recover the data from the backup copies and wait until PL5 actually handles simple keywords and the ‘Artist’ properly!
Additional comparison between before and after PL5 processing:-