| Summary: | HUB : extend metadata configuration panel to improve metadata handling while importing from file to database (and vis-versa) | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | oivanenko <oivanenko> |
| Component: | Metadata-Hub | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | anttiah, caulier.gilles, jason, kmm, languitar, rafael.linux.user, veaceslav.munteanu90 |
| Priority: | NOR | ||
| Version: | 4.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.0.0 | |
| Bug Depends on: | |||
| Bug Blocks: | 244224 | ||
|
Description
oivanenko
2011-02-09 14:50:10 UTC
I now have the opposite problem with Debian's 4:2.6.0-1+b1. The IPTC tags no longer are used as image tags, the headline isn't used, etc. I had relied on digikam mapping IPTC metadata into its metadata. I see no option for enabling it... An exiv2 interaction changed, maybe? IPTC metadata is deprecated now. XMP must be used instead. Why ? Because IPTC do not support UTF8 and has string sizes limited. XMP don't have these limits. IPTC still used to stored some reduced tags info, but not full Tags path. Gilles Caulier I have over 15 thousand images, some of which are on archival storage. You're telling me I have to reprocess *all* of them to continue using digikam? Thanks, but no. I'll find something else. Go to Tools/Maintenance. There is an option to sync metadata with database. Just take a care about Metadata/setup before. Gilles Caulier That doesn't do anything, as it doesn't import the IPTC tags, header, etc. Digikam isn't in charge of the archives; it's a handy viewer for more complex slices. Tools/Maintenance will synchronize XMP metadata with digiKam database information. This include Tags path. There is a Digikam XMP namespace for that : http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/XMP.html#digiKam Gilles Caulier But what I have is IPTC metadata, not XMP metadata. You're telling me I have to convert *all* my metadata even on archived files if I want to use digikam. yes, it is... Goodbye. AFAIK, IPTC import is (of course) still possible. Though that's not the original request here. Import from the tags and headlines is not working now. That's what the original reporter wanted, and the opposite of what I want... Jason: A simple test shows me that reading IPTC keywords is working. If you have an image where this is not the case with a recent digikam/libkexiv2, please post if in a new bug report. The original report here is quite different. I change the title to a more general wish: We allow to fine-grained configuration of which information is written to metadata. Add similar configuration to specify which fields are imported from metadata into the database. I agree, the auto-import of tags is sometimes very annoying. Here is another idea for controlling this behaviour: https://bugs.kde.org/show_bug.cgi?id=287510 *** Bug 336164 has been marked as a duplicate of this bug. *** *** Bug 196484 has been marked as a duplicate of this bug. *** *** Bug 244224 has been marked as a duplicate of this bug. *** *** Bug 289300 has been marked as a duplicate of this bug. *** Digikam 5.0.0 have the extended panel, which will allow you to select in which order and what digiKam will read and write metadata. |