In older sighting from 2016 you can still find in researcher comment, that it has been recogniced and named and approved: “Submitted on Thu Oct 06 12:21:42 UTC 2016 from address: 193.167.41.1 Meeri on Thu Oct 06 12:22:33 UTC 2016 Added to newly marked individual Phs216. Meeri on Thu Oct 06 12:23:31 UTC 2016 Changed state from unapproved to approved.”
I’m sure that before clicking “merge” Phs code and name “Iisakki” were showing normally.
Piia
If this is a bulk import report, send the spreadsheet to services@wildme.org with the email subject line matching your bug report
I was updating tags in the forum recently and it may have made recent posts less visible. I’m adding this reply to bring it back toward the top of the forum timeline. Thanks for your patience while we research this!
Tagging @jason to help me research this one. I also can’t find Phs216 in the list of individuals. Is it somehow possible it was merged with a different seal and no longer searchable under Phs216?
We found a bug, and we are testing a fix. We should deploy it early next week.
Long story short: in merging two individuals in Codex: if any exception/problem was encountered in the merge process, the old Sightings may end up in an unassigned state. Solution:
make sure any data problems during individual merging don’t leave sighting in an unassigned state but rather rollback to the original individual gracefully
If I remember correctly, the thing with merging was that I didn’t have the rights or permission to all sightings involved in the merging process. I see I don’t have editing rights to all other users, for example for Public user. Will that be a problem also in the future when trying to merge?