https://bugs.kde.org/show_bug.cgi?id=508060

            Bug ID: 508060
           Summary: When adding a new collection, tags are not associated
                    with images when using sidecars file and tags
                    hierarchy
    Classification: Applications
           Product: digikam
      Version First 8.7.0
       Reported In:
          Platform: Microsoft Windows
                OS: Microsoft Windows
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Tags-Engine
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

SUMMARY
Installer used: digiKam-8.7.0-Qt6-Win64.exe (official release) under windows
10. After installation, metadata configuration behavior "Write this information
to the metadata" are all selected. Also "Rescan file when files are modified"
is not selected (manual refresh). Sidecars file configuration "Write to sidecar
files": write to XMP sidecar only selected. Anything else in metadata is
default settings. In miscellaneous settings, behavior section, all setings
above red message "Warning: These settings makes startup slower" are
deselected. Initially there is no collection neither tags in the databases
(from clean install).

The image files collection has sidecars files in the form of "basefile.ext.xmp"
and the tags are fully qualified with tags hierarchy (using "/" character in
the tags hierarchy). The tags are only located in the sidecars files, not in
the images themselfves.
When creating a collection, the tags hierarchy is fully created in digikam, but
no images at all will have a tag (selecting no tags in tag tab will show all
images of the collection!).

The only  way i found to repair this problem after the collection was created
is to do a database maintenance in the "Sync Metadata and Database" option,
select it with sync direction "From image metadata to database", then magically
all images are associated with their respective tags!

It is like when the collection is created, if the tag hierarchy does not exist,
it cannot create the tag and associates it to the image at the same time. A
second pass through the database maintenance is needed to do the job. correctly

The bug is fully reproductible all the time.

STEPS TO REPRODUCE
1. Start a clean digikam installation
2. Configure it as explained
3. Create a new collection with images using only external sidecar files for
tags (using a fully qualified tag hierarchy)

OBSERVED RESULT
Not an image at all will be tagged, but the completly full tag hierarchy is
created as expected, simply no image will be assigned to any tag

EXPECTED RESULT
The images are associated to their tags in the hierarchy immediatly when the
collection is created the 1st time and does not require a database maintenance
which appears to be a little dangerous to use everytime the files change in the
collection to overwrite some database settings...

SOFTWARE/OS VERSIONS
Windows: 10
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to