Double Tagging of Memories Problem
Since the new Memories viewer is connected to the group trees, is this the right place to post problems and comments about it?
Macbook Pro, Apple M2 Pro, Retina Display 14-inch (3024 × 1964), MacOS Sonoma 14.1.2, Safari 17.1.2.
Starting in my gallery:
I add a tag for one person whose profile is in both my space and a shared group space:
The tagging is duplicated as seen here (if you look closely you can see the ID number is the same):
Expanding the Tag section, I see the tag in my private group is also there and also doubled:
I ended up with a total of four tags when I should only have had two.
Comments
-
I think that we should tag to only ONE of the copies of the persons and to choose where to show it with the "Visibility" feature. If people and different trees have the ID "linked" it should work.
0 -
I think that we should tag to only ONE of the copies of the persons and to choose where to show it with the "Visibility" feature. If people and different trees have the ID "linked" it should work.
I agree that that would be very handy if that were the way things worked. As things stand now, they should get tagging to work properly as currently designed.
0 -
Thank you for pinpointing this problem. When you report errors it reduces the time engineers spend trying to find them. Do remember that this is all experimental right now and still being coded! Thank you for your patience as we work through all the issues you wonderful testers are finding!
And Yes! @Gordon Collett for now reporting errors in the new Memories process should go here. We'll let you know if that changes.
0 -
Thank you, Gordon! The Memories team is aware of this issue. It's fairly complex to fix. We have details written in Jira (our bug tracking software) and meetings are being planned to investigate solutions.
I'll add your feedback as well, Bosch. Maybe we can do something about "linking" the different IDs before someone starts creating tags. Then we wouldn't have confusion when trying to select and add the tags.
Thanks again for your feedback and your patience! ~Stacy L.
0 -
@Gordon Collett This should have been fixed in a recent update to the system. If you find new occurrences, please create a new post in the Memory Viewer Feedback group.
0
