<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks all for having a look at this. My OP was due to a concern about metadata (focusing on keywords) inconsistency between digikam and ON1. I didn't understand what was happening and was looking for a solution/explanation, thinking that both should be using
industry standards for creating sidecars (ON1, as it appears, not). I thought that if in ON1, and while using one their editing tools I also wanted to modify/add/delete a keyword, description, rating, date ,etc, I could do that while in ON1. Likewise for digikam.
That wasn't working as I expected, getting a confusing output of incorrect ratings, missing/changed keywords, keywords entered in a raw photo showing up differently/not all in its jpg, keyword hierarchies being parsed into component words, etc. And, in my
experience, embedding/updating metadata to/from a jpg only served to transfer this mess from the sidecars to the jpg file.<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I now have a much better sense of the situation. Also, this is not just a digikam/ON1 problem. I have found sidecar/metadata management incompatibilities in other popular processing apps - DXO PL, Luminar, Exposure, to name a few. Through all of this though,
digikam has performed as the best DAM (speed, stability, interface, GPS/map functions, and yes, standards) for me, and I imagine for many others.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Now that I have a better understanding of what is happening I have changed my workflow to use only digikam for metadata management, including creating only the sidecars filename.jpg.xmp and filename.raw.xmp (filename.rw2.xmp in my case). I will not being using
ON1 any more to update these sidecars nor to create original sidecars, nor use digikam to modify sidecars created by ON1. Not a difficult decision since ON1's DAM capabilities, although greatly advanced over the past few years, are still (IHMO) quite buggy
- incorrect search results in keyword list, not finding keywords listed/visible for a photo, keywords deleted from keyword list (and photo, and sidecars) showing up in list again, etc.
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Since any photos processed in ON1 were saved as JPGs and/or TIFFs, and I'm not one to ever re-edit them (or would rather start from scratch if I did), I have no problem deleting whatever sidecars ON1 created in the past (using CMD prompt DEL+argument) to keep
conflicting .xmp and .on1 sidecars out of the directories. If I have a particular problem with a jpg photo's metadata being scrambled through previous joint access by digikam and ON1 I'm using exiftool to remove offending/all XMP and IPTC tags. Going forward
ON1 will still create its own .on1 and .xmp sidecars for metadata and parametric editing info. I will simply not do anything as a user to modify these files.<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Regards,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Alan<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Digikam-users <digikam-users-bounces@kde.org> on behalf of Gilles Caulier <caulier.gilles@gmail.com><br>
<b>Sent:</b> Wednesday, May 6, 2020 1:06 AM<br>
<b>To:</b> digiKam - Home Manage your photographs as a professional with the power of open source <digikam-users@kde.org><br>
<b>Subject:</b> Re: [digiKam-users] Keyword (metadata) consistency between programs</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Le mer. 6 mai 2020 à 08:49, Remco Viëtor <remco.vietor@wanadoo.fr> a écrit :<br>
><br>
> OK, so I had a look at those ON1 files.<br>
> First, those are *not* XML files, but look like json files.<br>
><br>
> Second, while keywords are stored, I'm not sure the hierarchy is preserved<br>
> (hard to see, as there's either no tree, or the tree has only one branch).<br>
><br>
> So, if I understand correctly what you wrote in the accompanying text, the<br>
> _1030666 sidecars were written by ON1. While the .ON1 file has two sections,<br>
> the .XMP only has one section (no separate "raw" and "jpeg" sections).<br>
><br>
> So from what you describe, digikam does *not* read the .ON1 files, which is<br>
> understandable, as they are not XML data. I don't think digikam reads json<br>
> format...<br>
<br>
Yes, digiKam support standard. XMP sidecar are the standard, defined<br>
by Metadata Working Group (including Adobe). XMP use XML format, not<br>
JSON.<br>
<br>
<a href="https://en.wikipedia.org/wiki/Extensible_Metadata_Platform">https://en.wikipedia.org/wiki/Extensible_Metadata_Platform</a><br>
<br>
There is no plan to support exotic sidecar file, as ON1 do. ON1 must<br>
use standards to improve interoperability, and not to re-invent the<br>
wheel...<br>
<br>
Best<br>
<br>
Gilles Caulier<br>
<br>
><br>
> It does read the ON1-generated XMP file, but that one is the same for both the<br>
> jpeg and the raw file, so keywords will be the same for both.<br>
><br>
> Remco<br>
><br>
><br>
><br>
><br>
><br>
</div>
</span></font></div>
</body>
</html>