hi! i checked into this and it appears the reason GR755 and GR803 were not showing up in the list was that the actual individuals for these 2 turtles were missing having their taxonomy set. therefore, they were not matching Chelonia mydas on the encounters.
i have set the taxonomy (see pages below) and they should now show up for this species.
hopefully this helps explain why some individuals might not be popping up in this list.
-jon
Hi all, this was helpful, thank you for adding in the taxonomy set!
This still happens when I match:
Hi Jo,
I see that both these encounters are owned by the primary ORP account and currently have the name
GR862 assigned. Were able to resolve this issue?
It should only occur if the logged in user doesn’t have edit privileges on one encounter or the other. Which account were you using?
Please send me links to the encounters or match results if this continues happening, it’s much easier troubleshoot when those are at hand.
Thanks!
Hi Colin,
I’ve manually assigned the ID to the turtle on that encounter and then assigned it to ORP in order to process it quickly.
Here’s an encounter I haven’t processed further after getting the error message on User unauthorised for encounter: https://iot.wildbook.org/encounters/encounter.jsp?number=25d09c56-f304-406d-a764-fb58b9930a4f
Hi Colin!
Unfortunately, the problem remains for all “junior” ORP accounts. These include:
ORP-Laamu
OS: OSX Catalina Version 10.5.3
Browser: Safari Version 13.0.5 (15608.5.11)
ORP-Lhaviyani
OS: Win10
Browser: Microsoft Edge
ORP-NorthMale
OS: OSX Big Sur 11.2.3
Browser: Safari - Version 14.0.3 (16610.4.3.1.7) AND Chrome - Version 92.0.4515.159 (Official Build) (arm64)
Each is signed in as researcher and runs into the same problem as detailed in the message above. Taxonomy is set correctly, as well as ownership of the encounter.
I am working on the main ORP account and have no issues.
OS: OSX Catalina 10.15.7
Browser: Safari 14.1.2
Thanks for the continued support, please let us know if you need more example encounters with the issue or similar!
Best,
Steph
Hello,
This is still an issue of ownership and regional permissions. The Laamu account did not have full regional access, so the encounter owned by ORP could not be modified.
All Wildbook permissions are controlled by ownership and regional management- there isn’t a way for me to automatically grant full control of all ORP members data to all other ORP members.
For now I’ve added the Maldives and Laamu role to the Laamu account controlled by Isha, so this particular linked case should be resolvable.
You should try the collaboration interface. In your user profile, there is a box where you can search for other users. Once you have found a user you can initiate a collaboration. This collaboration means little on IOT for viewing purposes as it is a more open platform, but you can also grant edit privileges. The receiving user must approve this request. If the team all initiates collaborations with each other it may resolve this difficulty for you.
If it does not for whatever reason, we will consider creating a regional role for every location ORP operates in and granting this to each member. This would effectively make you data admins for the entire region, and the issue might need to be revisited if another research group enters the area and is uncomfortable with it.
Thanks!
Hi Colin!
Thanks for the feedback.
I am having a little trouble understanding your answer though. Maybe I wasn’t entirely clear in the description.
So here goes:
One of our biologist uploads an encounter, thus has ownership of it. They run a match, but cannot assign the identified individual, which they were able to do in the past. They still are should be authorized for the encounter. Manual ID assignment is still possible. Only AFTER that encounters are assigned to the main ORP account and then it is correct that ORP users Lhaviyani/Laamu/North Male cannot edit it anymore or assign
Is the issue here not the ownership of the encounter but of the identified individual turtle? No, that’s not it, correct?
Since this is an issue for three accounts and not just the Laamu one, I do not think that overall admin rights are the way to go here.
Should I collect some example encounters with the issue to link here?
I will also give the collaboration a try, as you suggested.
Best,
Steph
Hi, @ORP-StephanieK !
Colin will likely get back to you very early next week if this has still not been resolved by then.
Thank you for the detail in your new response. I couldn’t tell from said response whether trying out collaborations has been a helpful avenue for you or not.
Please let me (us?) know if you try that out and are still having difficulty.
Thanks,
Mark
Hi!
Definitely will get back with feedback on collaborations asap - just send out the invites yesterday, team will try it out over the next days.
Best wishes,
Stephanie
Hello again!
Just a brief feedback: The collaboration does not seem to have solved the issue, below an example sent to me from the Lhaviyani account.
Kind regards,
Stephanie
Hi @colin
continuing with an earlier response from this thread.
I have the same issue where I can’t assign an ID to an encounter from the public that matched with one of our encounters. Would it be possible for me to get those privileges for Hawaiian turtles?
https://iot.wildbook.org/iaResults.jsp?taskId=5f756a04-caa5-43e6-970d-affa18de20d0
Thanks for your help!
Hi Stephanie,
Can you confirm that the collaborations have all been granted not just at view, but at the ‘edit’ level? That step is required to allow ID assignment.
The should be solved now through roles however. I’ve gone ahead and added roles for all Maldives locations and assigned them to all the ORP Maldives users I could track down. You can verify your account has these roles from your user profile page, and also double check the collaborations there.
I hope this solves your problems with assigning ID, please keep me updated.
Thanks!
Hi @noaahawaii,
I’m looking into solutions for your request. There is more complexity because there are
multiple organizations doing research in Hawaii for IOT.
Thanks!
Hi Colin!
Please excuse the delayed reply.
Looks like that actually solved our problem and ID assignment works now - thank you so much for the support!
Best wishes,
Stephanie
Hi @colin !
Any word on this yet? I’m hoping to start having citizens upload images from around the Main Hawaiian Islands to match with ours in our dataset and to be able to assign ID’s to them.
Thank you for the help!
Hi @noaahawaii ,
I’ve responded to you with some details about this issue in a private message. Thanks!
Sorry about the long wait. We’re going through our ticket backlog and reviewing unresolved issues.
Updated ticket link: IOT matching and bounding box issues · Issue #269 · WildMeOrg/Wildbook · GitHub
After a lot of validation work, we’ve confirmed that this has been addressed in other platforms, but it wasn’t reported in the original ticket. Are you still experiencing any of these issues in IoT?
