-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to get detections from outside own receiver network #277
Comments
No idea honestly - I'm not the admin of the ETN database @bart-v and Francisco Hernandez should know more |
Whoops, thanks for the reference! |
Hi, Marine should have sufficient rights. She has access to FISHINTEL and as teh tag belongs to that project she should see all detections of that tag... |
Hi everyone, I am not able to visualize this fish from neither the RStudio server nor the Lifewatch data explorer. There is definitely an issue here. Thank you for your help. |
Hi,
Can this be checked soon? |
Thanks for digging that up Claudia, I'll look into it this week and see if I can estimate when it'll be fixed. It's on my radar! At the moment I don't really understand how the tag type mapping can stop certain detections from showing up. Do you have any more information? @peterdesmet Any insight would be highly appreciated :) |
I also don't see how the tag type can affect this. |
Summary of a reported issue from an email thread on the 2nd of March 2023: @jreubens , @cfmuniz, and others.
Marine Gonse reports:
Francisco Hernandez:
However, there should be 6 detections for that tag :
According to @jreubens this might be because currently users can only detect detections from their own receiver networks, if this is the case this would be a bug as the intention is that users can retreive detections for their own projects from any receiver network.
Another explination could be that Fransisco and Marine possibly do not have sufficient rights to
OPI-602
These user limits are regulated on the database side. Do I understand this correctly @salvafern ?
The text was updated successfully, but these errors were encountered: