What Wildbook are you working in? ACW
What is the entire URL out of the browser, exactly where the error occurred?
Match #5 here: https://africancarnivore.wildbook.org/iaResults.jsp?taskId=9a815567-3cb9-4389-84b9-3e14737db78e
Displays the ID as a UUID rather than the standard name in this dataset (CH00----)
Can you describe what the issue is you’re experiencing?
The researcher is following a regimented approach to her matching in this dataset - she starts with an individual ID (in this example CH00060) and selects a viewpoint encounter and runs matching against it to find all the unassigned matches in the database. When she determines that a proposed match is a match, she confirms the match on the match page.
In this case, she’s found an ID’d individual listed in the potential matches (#5 in the url above) that doesn’t have the standard naming convention but instead has a UUID. When I look at that Marked Individual page, I see 2 encounters assigned to this individual.
I understand that this means that no CH00— name was assigned so the system applied a UUID but I don’t know how this can be done?? What user error can cause this to happen? And is there any way to figure out what the CH00---- id was originally?
These encounters were not uploaded with IDs - I can tell because the ID’d individuals in this dataset were uploaded without the Occurrence ID naming convention that you see in these two assigned encounters; they had random UUID strings for OccIDs. So somehow, these 2 encounters were assigned this UUID as the Marked Individual ID without the user noticing.
Is it user error or a system issue?