Bug 318473 - Dont import keywords from Windows Keywords
Summary: Dont import keywords from Windows Keywords
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Hub (show other bugs)
Version: 3.1.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-17 01:15 UTC by Bernardo
Modified: 2020-08-30 15:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernardo 2013-04-17 01:15:41 UTC
When new Keywords are add by Windows ( Windows Keywords ) digikam dont get these new keywords.

When a file is indexed at the first time at digikam, and only have keywords at Windows Keywords fields, digikam is able to get these Keywords. 

If you edit any metadata and apply this change to the image (at digikam), and then is add a new keyword to this image at Windows, digikam is not able to get this new keyword from the file.
digikam seems to embed new key words at the files properly but dont get new ones embed by windows at the fields:
Windows keywords;
IPTC - IIM Application 2 - Keywords
Dublin Core - Subject

on the other hand Windows is able to read new tags embed by digikam.

It's useful for those like me that share photo albuns with many people and these people use others metadata editors than digikam.

On rating it does't happed, they are perfertly intercompatible

Reproducible: Always

Steps to Reproduce:
1. save at a album a image that only have Windows Keywords
2. The digiKam is able to get these Keywords from the file to the database when clik "read metadata from file to database"
3. Edit any metadata (like Title or Caption) and apply it to the file
4. Put a New keyword at windows
5. At digiKam, try to get these new keywords at "read metadata from file to database"
6. Nothing happend.....digiKam can't get these new keywords embed by Windows.
Comment 1 caulier.gilles 2013-11-21 22:39:15 UTC

*** This bug has been marked as a duplicate of bug 320185 ***
Comment 2 caulier.gilles 2020-08-30 15:57:26 UTC
Fixed with #320185