SeadragonSearch- system duplicating encounters

What Wildbook are you working in?


What is the entire URL out of the browser, exactly where the error occurred?

Complete encounter:

Duplicate encounter of one photo:

Can you describe what the issue is you’re experiencing?

When I submitted two photos together, two separate encounters were created: one with both photos and one with only one of the photos. Something similar was happening a while back where deleted encounters were reappearing in the unapproved encounters box with 2-3 duplicates. See this support convo for reference:

Can you provide steps on how to reproduce what you’re experiencing?

It may or may not happen when submitting a new encounter.

If this is a bulk import report, send the spreadsheet to with the email subject line matching your bug report

Hi Chrissy,

This is the system working as designed, though it is a false positive by the detector (rare when they’re overlapping, but it happens). The detector found the same seadragon twice in one of the photos, and since 2+ animals in one photo causes the Encounter to be cloned to hold the second annotation (i.e. it’s a different animal), you see the second Encounter created to hold the additional annotation. You can safely delete the second Encounter.


1 Like

Thanks for the explanation, Jason!

Hi @jason ,

Just wondering if this is the same thing you described above happening?

Complete encounter:

Duplicate left:

Duplicate right:


One more- just want to document in case something else is going on! Thanks.

Complete encounter:

Duplicate of one photo:

This looks like we found a head and a body in the right side photo but two heads in the left. The second head can be safely ignored by deleting the cloned Encounter. I would consider this a false positive. If we see more of these trending, we may need to retrain the detection model or double check our settings.

1 Like

Hi @jason ,

I’ve had a couple more of these instances- is it helpful for me to keep reporting them in this chain? Thanks!


Yes, please report them here!