how to migrate xmp to raw.xmp

[frederic chaume]

Hi Maik,

Effectively, it would be the best solution.
difficulty would happen when conflict occurs: example file.xmp and 
file.raw.xmp exists both in the same folder.
My understanding is that such conflict may exist when ,after unsetting 
the parameter "sidecar files names are compatible with commercial 
programms", any change made will conduct to create file.raw.xmp even if 
file.xmp exist
as part of the solution such case could be handled when metadata update 
is needed , renaming existing xmp instead creating a new raw.xmp


frederic



Le 24/09/2024 à 12:29, Maik Qualmann a écrit :
> Probably the best and simplest solution is that we write a module for the
> maintenance tool that does this job.
>
> Maik
>
> Am Dienstag, 24. September 2024, 08:39:18 MESZ schrieb frederic chaume:
>> let me ask it more simply
>>
>> after unsetting "sidecar files names are compatible with commercial
>> programms", how to migrate my file.xmp into file.<raw type>.xmp under
>> windows
>>
>> regards
>> Frederic
>>
>> Le 22/09/2024 à 15:37, frederic chaume a écrit :
>>> Hi all
>>>
>>> the setting "sidecar files names are compatible with commercial
>>> programms" was set to on, but because of some compatibility issue wih
>>> DXO, I had to set it off.
>>>
>>> the consequence is that I need to migrate the sidecar files name to
>>> the new format (file.<RAW type>.xmp)
>>> another consequence is that the "finding new items" is taking lots of
>>> time , and I prefered to cancel it as I suspect the DB is updated base
>>> on the new configuration ,and as the new xmp file is missing , then it
>>> is removing the metadata. May be someone can confirm the behavior
>>>
>>> FYI I'm using DK 8.4 on windows 10
>>>
>>> Based on this, I guess that the best solution is "just" to rename
>>> file.xmp by file.ORF.xmp  for ORF Raw file and the same for any other
>>> raw file type I have on my PC
>>> I started to create a script in powershell, and it confirms my analyse
>>> , some pictures has lost metadata and then recover them as soon as the
>>> xmp files are renamed. But this  is painfull as I'm not a dev expert
>>> in Powershell and as there are many cases to handle: ORF.xmp already
>>> exist , xmp corresponding to different raw type, ....
>>>
>>> so before spending all my time in this exercise, I'm wondering if
>>> someone have any idea to make it more simple ?  Is there a procedure
>>> in DK to perform this migration ? may be someone falled into this
>>> scenario already and have experience to share ?
>>>
>>>
>>> thanks in advance for any advice
>>>
>>> Frederic
>
>
>