Sharkbook
Hi, I have full admin access, but today I cannot add spot maps in sharkbook. It says “Access Denied”.
Access Denied
You do not have permission to access this resource or execute this command.
This is the encounter: Sharkbook: Wildbook for Sharks that I tried to create a “spot mapping” on.
It looks like the restart fixed the access issue, but now I see that images aren’t loading on the spot mapping workflow. I’ve let the devs know and they’re looking into it.
Ok, this has now been fixed. Let me know if you run into any other issues spot mapping the encounter.
Hi Anastasia - the problem still is happening. It says access denied for me when I try to do spot maps
Thanks for letting me know. We’ll keep looking into this. I’m not able to replicate the permission issue even though we’re both admins. I’ll let you know as soon as I have an update.
Actually, I think this could be a caching issue. Do you mind trying a hard refresh in Sharkbook? On Windows, hold down Ctrl and then press F5 on your keyboard. On Mac, hold down Cmd and Shift and then press R on your keyboard.
That didn’t work unfortunately
There is something going on where sharkbook.ai and www.sharkbook.ai are being treated differently in the browser. Can you try adding “www.” in front of the Sharkbook URL and trying the spot map again? This should help as a workaround for now. I know browsers are kinda mysterious about this and sometimes obscure the full URL and tend to “remember” what you entered before.
Unfortunately still no joy. Have cleared cache again too and tried logging onto a different browser. I am using www.sharkbook.ai but no luck
Thanks for the update and the detailed summary of the other steps you tried. We’ll keep working on this and I’ll follow up with you when I have a new update.
We should have a resolution for this by the end of the day, Pacific time zone.
This behavior should now be fixed. Let me know if you run into other issues.
I have cleared my cache but it still comes up with “access denied” when I try to perform spot mapping.
Its a bit confusing, because when you first log into sharkbook it has the new look. So you log in and when it loads it includes in the home page www.sharkbook.ai/react/home and within that site you cannot see the legacy search results. So you have to remove “react/home” from the web address which then makes sharkbook look more how it used to. And that is where in the menu there is the search results (legacy) and so I think the issue of it jumping from old to new is perhaps what is causing it?
Either way I really need your help in resolving this since the new MiewID is very bias and is simply not working on a number of sharks and I desperately need the old algorithms so that I can ID those sharks. By doing this hopefully it will train MiewID more and more too - but without the ability to do spot maps its leaving us making a larger volume of sharks unresolved. If you could help this issue before the break up for Christmas (in Australia we have 2 weeks off work and I wanted to spend as much time as I could to get through the workload).
Thank you! I know you guys are trying hard - hopefully we will get there - I cant help but think its something to do with there being an old and new site working concurrently though?
Thanks for the update! I’ve shared your feedback with Jon and Jason, who are still working on Sharkbook this morning. I’ll let you know when I have another update.
Hey @Sarah_Aus_SpotaShark do you have time for a quick call with me and Jon today? We’d like to have you screenshare with us in real-time to help us debug the spot map issue for you since we haven’t been able to replicate this on our side.
Hi Anastasia - I can do this tomorrow which would be your evening and my morning? Let’s do it together whilst doing a screen share!
Awesome. I’ve emailed you my scheduling link.
Thanks for meeting with us today! To summarize our findings:
imageprocessor role. This was the role that gave a user spot mapping permissions. Standardizing Sharkbook roles to remove this didn’t affect users until the latest Sharkbook upgrade. We’re working to roll this permission into the admin role.