What is the entire URL out of the browser, exactly where the error occurred?
All bulk imports with the Occurrence ID beginning with: BPC_OvrvwWtd_Fldr
Which are all under the same User ID.
Ex’s:
Sighting / folder 1: Wildbook for Carnivores | Login
Sighting / folder 406: Wildbook for Carnivores | Login
And all the 384 sightings in between.
I’m trying to give OrgAdmin access to a student working on these folders, on behalf of the data owner, who has the User ID under which this imageset was uploaded. The student needs to be able to re-run each of these folders through Identification so that she gets fresh match results to review & ID.
However, when I give her OrgAdmin access to the same org (BPC/WE), she is still not able to re-send these bulk imports through matching.
I believe the issue lies with the Org / affiliation that was used when these uploads were first done - it was “BPC”.
When BPC’s parent organization re-branded to Wild Entrust, we updated the Organization name in the User Management area to BPC/WE.
I believe that updated Org name created a disconnect between the org on the encounter records in all those sightings and the user rights management under the newer BPC/WE.
Is there an easy way to fix this so that I can give access to this student (and others who are working for the same org) OrgAdmin level access that gives them the ability to access the Image Analysis functions on bulk imports?
Do you midn sending the username via email? orgAdmin should unlock the resend to ID function irrespective of organization. I’ll need to look more closely at the account.
Hi @jason - just realized that the data owner also does not have the ability to run IA on his own bulk imports, despite also having OrgAdmin access. I’ll send the user ID through email.
It looks like we were still filtering this function to admin only. I have extended the option to orgAdmin, but treally we could make this a researcher-level function at this point. What are your thoughts?
Also, can you please test that at least orgAdmin allows re-ID for bulk imports now?
@jason, it’s funny though, because I’d given other users OrgAdmin previously and they’ve been able to send their bulk imports through IA without the full Admin access. These two users @BPC are the only ones who’ve had this issue.
Hi @jason, it looks like the problem still exists. I logged in as the user and selected a sighting, clicked resend to identification and got this message:
Shortly after the error message appears, the page resets and the “resend to identification” button reappears, which I believe is expected behaviour.
I can confirm that this user ID, which is one of the 2 that are having this problem, has OrgAdmin level access.
Logged in using my own account, I am able, as expected, to re-send the same sighting, to identification.
Would you be able to share those researcher-level credentials separately via email with me? I believe I can addresd this quickly but want to ensure I am solving the right problem.
