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.
For “singular” tags that only have one value, like
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.
For “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.
(This is one of the sticky bits that I just solved with v2.0: it’s really irritating to, say, remove a tag from an asset, import an old backup drive that has an old copy of that image, and have those changes quietly “undone.” v2.0 adds a new
AssetRevision model that records whenever you make changes via the PhotoStructure UI so it can remember “user intent” and avoid these gaslighting moments)
As always, if you find that PhotoStructure isn’t working correctly for you, please tell me and we can look at what’s going on!