Encounter assigned user incorrectly set to public

Bug Reports
, ,
1

In which Wildbook did the issue occur?

Internet of Turtles

What operating system were you using? (eg. MacOS 10.15.3)

Various

What web browser were you using? (eg. Chrome 79)

Chrome145

What is your role on the site? (admin, researcher, etc)

Researcher, orgAdmin

What happened?

When uploading an encounter, sometimes the submitter information is not retained and instead the Assigned User is set to “public”. Subsequently, the submitter cannot edit the encounter anymore.

See for example:

https://iot.wildbook.org/react/encounter?number=5e19f742-d5d9-4eb7-acb3-be77e7595a61

https://iot.wildbook.org/react/encounter?number=46737e74-e292-4d84-9d36-fffcb5b9722e

The original issue is most likely an unstable internet connection leading to incomplete data submission to the server. Nevertheless, in the past I could edit these encounters for the Maldives for example, and now I can no longer. I assume this is because of the implementation of stricter data protection on IoT.

Is there a way to request edit access again for such encounters though? Otherwise, there is no way to remove “clutter” and accidental duplicates.

What did you expect to happen?

To have the option to re-assign the managing user

What are some steps we could take to reproduce the issue?

No sure how to recreate the initial unassigned encounter.

Thanks in advance for the help, as always!

Steph

2

This is likely a bug. Is it just the managing researcher you can’t edit or does it block you from editing other parts of the encounter. Does it let you view matches?

3

I can’t edit any parts of the encounter or view matches.

4

Here is another example, submitted by AMC-Kanuhura account which the ORP account is collaborating with. Neither account can edit anything.

https://iot.wildbook.org/react/encounter?number=bbb86ba5-2feb-4c4d-a9be-f4112ded8317

5

Thanks for confirming. I’ll work on this today.

6

Additional testing uncovered more layers of odd behavior related to public encounters. I’ve made a ticket for the issues: Permissions related to public user are too strict · Issue #1481 · WildMeOrg/Wildbook · GitHub

7

Since this may take longer than I anticipated to fix the root of, do you need me to assign these encounters to ORP?

8

Thank you - that would be much appreciated.

1 Like
9

I’ve updated the managing researcher. You should be able to edit these now!