Multiple copies of same annotations Seal Codex

What Wildbook are you working in?
Seal Codex

Can you describe what the issue is you’re experiencing?
I noticed, that a seal sighting with only 2 photographs of the seal, has multiple copies of annotations of each photo. I have not seen this before. What causes it?

Sighting page:
https://seals.wildme.org/sightings/df5678f4-70e5-4e55-a9f5-d826cd7fc801#overview

Annotations:
https://seals.wildme.org/sightings/df5678f4-70e5-4e55-a9f5-d826cd7fc801#annotations

*Edit
My co-worker also told me, that this is not just one case, this has been happening a lot while using the identification.

Best regards,
Piia

Hi @PiiaMutka

Thanks for letting us know. Can your coworker also post their examples in this thread so I have more data to share with the team to address this bug?

Hi there, @Anastasia @PiiaMutka

I have found a few examples of the same issue
https://seals.wildme.org/sightings/b5029da7-8d5c-4b51-b4bb-b0d81b150de0#annotations
https://seals.wildme.org/sightings/e6a7fb2e-a705-4a64-adb9-65fb1a953cfa#annotations
https://seals.wildme.org/sightings/5c6f0f65-d8b5-42ca-8be0-170a1a31e63e#annotations
https://seals.wildme.org/sightings/f16253be-c5a5-4c8b-b3de-8d3e0329d959#annotations

I found that, with these cases, the identification returns a match of the same photo (one of the duplicates) rather than a match to the individual (if that makes any sense at all…!)

Many thanks,
Mairi

Thanks so much, @myoung! That’s definitely not how it should be trying to match individuals. :sweat_smile:

Just to make sure I’m documenting this correctly, when you add one annotation, the system creates 3-4 duplicate annotations each time. Is that correct? I want to make sure I’m describing the steps correctly so we can reproduce it in testing.

Yes, that is correct. Although its not every time - it seems to happen maybe 1 in every 10 that I do. And each time a different number of duplicates (but normally around 3-4) Thank you :slight_smile:

Thank you! I’ll let you know when I have an update on this.

Hi @PiiaMutka and @myoung

This issue appears to have been resolved with the latest Codex release.