| Summary: | Unwanted tags Import due to XMP sidecar settings. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | George Orwell <apprendista.programmatore+digiKam> |
| Component: | Tags-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.7.0 | |
| Sentry Crash Report: | |||
|
Description
George Orwell
2024-09-29 10:09:57 UTC
Hi, No. AutoTags feature must be started manually from the maintenance tool. The tags created in the database are certainly imported from the file metadata whil scanning at startup. These tags have been probably creted by a 3rdparty application. Best Gilles Caulier (In reply to caulier.gilles from comment #1) > Hi, > > No. AutoTags feature must be started manually from the maintenance tool. It should be so, yet I found them > > The tags created in the database are certainly imported from the file > metadata whil scanning at startup. These tags have been probably creted by a > 3rdparty application. > > Best > > Gilles Caulier Before the update, they were not there. what third-party applications should have done this? The behavior is caused by a different sidecar setting (now correct with digiKam-8.4.0) You have created sidecars in 2 formats in the past, depending on the sidecar setting for compatible sidecar names. Now your previous sidecars have probably been scanned. Set the sidecar setting according to the third-party programs you are using (BASINAME.xmp or BASINAME.EXT.xmp). You will have to clean up the tags manually now. Maik Well, so to speak, after wasting an entire afternoon, I hope at least the problem will be fixed in the next version! |