| Summary: | Duplicate tags created with "\" as separator since upgrade to 8.3 | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Jens <jens-bugs.kde.org> |
| Component: | Tags-Manager | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.3.0 | |
| Sentry Crash Report: | |||
| Attachments: | Example screenshot of issue | ||
Read Bug 472914 Maik Thanks, I have. But I'm a bit confused ...
does this mean I have to rename & fix my >500 name tags manually?
If so, which ones ("/" or "\" variant)?
And what about name/face tag hierarachies, can they still exist? Can I still have a "People/Family/John" and a "Work/Colleagues/John"?
Another explanation: you entered a path for face names, which older digiKam versions did not check. Only names are expected in the face metadata. When importing, the slash is converted to a backslash so that we get a "whole" name, which now appears as a tag. You must correct the face metadata of the affected images. You can still have different "John", but the face metadata will only say "John". Only a corresponding tag metadata entry will contain the full path. Maik OK, this is understandable, but I actually loved the possibility to organize my face tags in a hierarchy directly upon creation. No way to do this? You can continue to do this. Only the images with face metadata saved with a slash require the names to be re-entered. The fact that the people's names still appear in a hierarchy is ensured by standard tags. Maik I would have to rename & fix several 100 face tags, this would take me several hours Can we automate this using a SQlite script or similar which just does it directly in the SQLite database? If you can give me some details about the SQL structure I can perhaps whip up a script, which in turn may help others. |
Created attachment 164605 [details] Example screenshot of issue SUMMARY Since upgrading to the newest 8.3.0 pre-release appimage, my tags directory has blown up because many tags (not all) have been duplicated with a backslash as the separator, in addition to the correct "/" (which gets interpreted by Digikam as a hierarchy). See screenshot. STEPS TO REPRODUCE 1. Install Digikam 8.2 2. Create some tags 3. Upgrade go 8.3 pre-release (December) SOFTWARE/OS VERSIONS: KDE Neon 22.08 LTS, Digikam 20240101 (911d1a7c02b08) appimage