It should be no problem if the structure in xmp is one on one the same.
And that’s a problem apparently for company’s. i would say if you can read a certain xmp you must copy the writing manner. and do so accordantly when updating a xmp.
If DxOPL has a good UI in editing metadata and a full organising structure for keywords, iptc-templates, colortagging and ratings i don’t need “bridge” other then managing my other files as video.
but if “DAM” applications are corrupting each other as fighting allycats then it start to be redundant features.
in dual mangement i understand that if i start culling in FRV then an xmp is created. (only rating and colortagging (future) step 2 now in bridge because of the better overview and structure act I do keywording and location naming. (GPS is trickier because copy paste google coordinates doesn’t work well. (hours and minutes vs longitude latitudes.
Step 3 would be in dxopl, during editing adjust rating and maybe add or correct additional information.
This would work fine if dxopl adopts and maintains the hierachy and structure that bridge and FRV set up.
Then you wouldn’t have to go back to bridge for addtional iptc editing.
No it should just read and stop thinking when you add non.
(at this moment i need to drop google gps in dxopl and copy the translated degrees in bridge and continu in bridge in order to keep my xmp’s save.)
So that would be the only adding in the database. (and it is then doubled by bridge probable in an other line in the xmp…
anyway, my backup is useless because i just was in the middle of rearanging and adding iptc data. it’s easier just to start over and run the hole system again wile adding and cleaning.
My frustration is because of that there have been plenty of warnings during the EA testing time by people who really knew what they were talking about, iptc managment and metadata managment. tranfer and crosover those kinds of problems. I kept out of the details because user is something different as programmer but unfortunately it’s not really stable after delivery.