

I think this is as "universal" as it gets.When assets are “re-tagged” by sync, PhotoStructure re-reads the tags (and sidecars) from all asset file variations, so editing any variation may work, but it depends on the tag.įor “ singular” tags that only have one value, like Make, Model, and captured at, PhotoStructure uses “first one in wins”, where “first” is based on variation ordering: so if you edit the Make of the non-primary variation, that edit will be ignored.įor “ aggregate” tags, like Keywords, PhotoStructure aggregates all the keywords it can find from all variations, so if you delete a keyword from only one of the variations, the keyword will still show up. xmp file with the face tagging information. Now you should have all your images in a folder, where each image has a corresponding. The way digiKam does that should be good enough. To be safe you could make all your photos read only, and then choose option 4 (or simply choose option 2). Tagged: face tags, metadata working group, MWG, people tags.
Digikam face metadata plus#
This gist exports the face tags from Picasa to the digiKam database directly, without touching any photos. DigiKam refers to whatever directories it finds within your image directory as an Album, and it parses each image file, along with its native metadata plus metadata digiKam allows you to add, into a thumbnail view.When you do a websearch for " digikam face tag import" you'll find a few methods that relate to Picasa: You're looking to move away from Picasa to a cross-platform solution, which digiKamoffers.īelow information is pieced together from the internet, I haven't tried anything, but from the descriptions it seems it will do what you want.
Digikam face metadata update#
To ease the deduplication process you want to have a "static" hash for each photo, even when you update the metadata of the photo. From your comments I understand you currently have an image library in Picasa, with photos which might become duplicated in the future (due to re-downloading).
