| Summary: | Tags Manager's Sync Export DB to metadata, mirrors XMP but it only appends IPTC keywords data | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | GPSanino <gpsanino> |
| Component: | Tags-Manager | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | caulier.gilles, freisim93, veaceslav.munteanu90 |
| Priority: | NOR | ||
| Version: | 4.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.3.0 | |
| Sentry Crash Report: | |||
| Attachments: | image file with IPTC and XMP metadata to test on DK4.0.0 | ||
|
Description
GPSanino
2014-06-16 19:02:16 UTC
Created attachment 87221 [details]
image file with IPTC and XMP metadata to test on DK4.0.0
this file is for testing purposes only.
Just try to read the metadata from the attached file into database using DK 4.0.0. It has more info on the IPTC than XMP, but the database will only collect metadata from XMP and not IPTC sections. Also, changes (rename/delete/adds) on the tags from DB, when saved into the image's metadata will only mirror DB and XMP Metadata, while on IPTC changes are only appended. yes, by preference order, metadat in DB are filed by XMP and after IPTC if XMP is not available. Why? Because IPTC has serious limitation that XMP don't have. Typically Metadata Working Groug recommend to synchronize XMP with IPTC for the best compatibility. I recommend to revise your workflow if your initial metadata DAM do not respect this rules. Gilles Caulier Gilles, if I understand properly, this means that IPTC is _*ignored*_ if there is something XMP on the file's metadata. So, I should be ok after cleaning the IPTC metadata with DK 3.5.0;... because I have no clue about how to synchronize XMP with IPTC. My surprise here is because I do not recall have used XMP before. I have not enabled to write on XMP side cars neither on my DK settings. Then, I do not know how metadata showed up in XMP on my files. I guess that happened during the sync export with Tag Manager with DK4.0.0. I am glad that DK 3.5.0 still reads the IPTC section so I can try delete its obsolete content. However, this fix seems only temporary since I may have again the same problem (not mirrored IPTC/XMP content) next time I re-arrange the tags tree and save to metadata. I wonder how in DK4.0.0 we will be able to clean IPTC data as we used to do in DK3.5.0. From your explanation I am not sure to understand if this will be treated as a bug or this is just the new way things are. Maybe I should see this inconsistency as fine since now I have XMP on my files. This is important for me because I have connected Digikam4.db file with LibreOffice.base for further queries, data analysis, etc. Now I know I have to change the used fields to retrieve data to only XMP fields and not IPTC. You saved me a lot of problems by telling me this. Thanks a lot Gilles gps On 06/16/2014 04:27 PM, Gilles Caulier wrote: > https://bugs.kde.org/show_bug.cgi?id=336328 > > Gilles Caulier <caulier.gilles@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |caulier.gilles@gmail.com > > --- Comment #3 from Gilles Caulier <caulier.gilles@gmail.com> --- > yes, by preference order, metadat in DB are filed by XMP and after IPTC if XMP > is not available. > > Why? Because IPTC has serious limitation that XMP don't have. Typically > Metadata Working Groug recommend to synchronize XMP with IPTC for the best > compatibility. > > I recommend to revise your workflow if your initial metadata DAM do not respect > this rules. > > Gilles Caulier > Fixed in 4.2.0 |