https://bugs.kde.org/show_bug.cgi?id=472914
--- Comment #7 from deryk.lis...@marl.co.uk --- Thanks for the update. I think I understand now! From an end user perspective my main concern was just the end result: whether I was stuck trying to tag a few hundred people but have them all listed in one lump rather than be able to group them into "Staff", "Public Figure", etc. Having no structure to them would be a nightmare. As we're looking at it from different perspectives, your comment from your perspective of "that's not a bug" worried me that I was stuck having to completely rethink the structure. As it turns out, it seems what I want *is* achievable, I've just been creating the "Parent" tags (folders, so to speak) in an unexpected way that put a face tag of say "Famous\King Charles" into the database whilst the tag side of things sorted itself out and hid the problem. I uncovered the symptoms when wanting to copy face tags from one photo to another and hearing it was only possible via exiftool and doing that (so copying the metadata from photo A to photo B then loading it with the reload from file menu). To me my attempted usage makes sense, as it's how it can work throughout the UI - when creating a new tag directly on an image, the UI invites you to create a tags hierarchy like "Country/City/Paris" by typing it that way and it creates the whole structure if it's missing (sort of like a mkdir -p). So this is how I created my first staff tag - I typed in "Staff/Fred Smith" into the face tagging UI which "works" superficially (but breaks things underneath). When I was experimenting just now and pre-created my structure (including names) in Tag Manager first then just *selected* them when face tagging, I'm finding it works fine and still keeps the grouping. But selecting names that existed from when I did it "wrong", even without typing any slashes into the face tagging UI, pulls the incorrect backslashed-form from the backend somewhere. I have a lot of broken face tags in this way at the moment but it seems I have a workaround to fix them: 1. In the People UI, rename say "King Charles" to "King Charles II". In the metadata, "Region Name" and "Region Person Display Name" change from "Famous\King Charles" to "King Charles II". 2. Rename him back to "King Charles". In the metadata, "Region Name" and "Region Person Display Name" change from "King Charles II" to "King Charles" (so it's now corrected) So it looks like I can repair them all "fairly easily" by renaming them in the People UI and just adding a 1 on the end or something and then renaming them all back again, whilst retaining the hierarchical tag structure I wanted. The obvious flaw here in face data being flat whilst the associated tags can be hierarchical, is when you have a John Smith under "Famous" and a different John Smith under "Staff", it's the same name so seen as the same person. Luckily not a scenario I've had to deal with yet. -- You are receiving this mail because: You are watching all bug changes.
