If you check your sidecar files (.dop and .xmp), you’ll find that DPL5 writes keywords to its .dop sidecars too - have a look at the screenshot above!
Before DPL5, Keywords were not transportable to newer versions of DPL except through the database. Now, keywords travel in .dop sidecars too…they just don’t reach their target, which in this case, is a dot update to DPL5.
As far as I am concerned, I expect DPL to be able to update its database with whatever information comes along in the files. As I’ve seen, this is not (yet) the case. Maybe it’s only a matter of checking a version number or timestamp, maybe it’s something else, whatever the cause, DxO should fix it.
Test on DPL v5.0.2 Win
I don’t know what my test is worth but I manually add a keyword in the * .dop and imported this one and the keyword was not added to the image.
I had also modified another parameter (WatermarkActive = false) to test and this one was has been modified.
Thanks for testing this. It looks like this is a general issue or design decision.
So far, .dop files have not been able to be a “distributed database backup”. If PhotoLab writes settings and metadata to the sidecar, but cannot import all it wrote, we’re still using a system that does not take advantage of its own possibilities…
We can automate .dop sidecar import/export - but import ignores metadata
We can back up the database - but we cannot automate it
And then there’s history…while advocating its introduction a few years ago, I can do without it, specially in the current super-granularity.