Unwanted Virtual Copies and Moving DxPL edited images (DOPs) between System - Revisited

@JoJu The good news is that you don’t really need to know too much (sorry that sounds a little patronising and it actually wasn’t originally intended too).

DxPL is aware of the changes and providing the database upgrade goes O.K things work well, but there were hiccups going from PL4 to PL5 for some and ‘Projects’ were lost on at least one occasion and if the PL4 database was not upgraded successfully then any keywords that were only held in the PL4 database would have been “lost”, i.e. they were confined to the database on PL4 and never made it to the DOP.

The actual edit formats appear to change from one DOP write to the next!!??

But the overall format can be summarised as

Part of a Python program to hunt out the bits I am interested in but I need to add IPTC for the sake of completeness!

Not really, the main issue with PL5 was the change with respect to what could be relied on from the DOP and the only other thing was the keyword formatting which up until PL5.2.0 conformed to the same formatting as Lightroom and IMatch with one option selected and after PL5.2.0 only conformed to IMatch with another option selected (or de-selected?) and in all cases with all elements in a hierarchical key selected in DxPL it conforms to Capture One keyword formatting!

The export format is the same as above and has not changed since at least PL3 right up until the change above on PL5.2.0.

The problem has been the forum posts like yours that simply spread confusion from people who are intelligent enough not to be confused. It is possible that DxO considered their documentation to be sufficient but the number of half-truths and downright misunderstanding that still seem to abound is …

So this is from a recent post and I believe it to be accurate, all determined by empirical evaluation, I have never seen the code nor been given any more information than any other users!

So for what it is worth