You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has been reported but I have not tried to replicate this b/c... it's very hard to set up repro conditions for bugs with trusted projects, so that's the first hurdle here. Setting up test data manually will require making a collection project, turning on user trust, joining the project with another account and trusting the project, and using that other account to add an observation whose obscured coordinates are outside the project place boundary but whose true coordinates are inside the boundary, so the observation will appear to be in the project to project owners and curators, but outside to everyone else. The reported symptom is that observations like this appear at /observations when an owner searches for obs in the project, but the species count does not include those obs. I am exhausted just typing that.
The good news is that there are already some fixtures you can probably use to make a real test (check out this one for an example). The bad news is that that's the only good news.
This has been reported but I have not tried to replicate this b/c... it's very hard to set up repro conditions for bugs with trusted projects, so that's the first hurdle here. Setting up test data manually will require making a collection project, turning on user trust, joining the project with another account and trusting the project, and using that other account to add an observation whose obscured coordinates are outside the project place boundary but whose true coordinates are inside the boundary, so the observation will appear to be in the project to project owners and curators, but outside to everyone else. The reported symptom is that observations like this appear at /observations when an owner searches for obs in the project, but the species count does not include those obs. I am exhausted just typing that.
The good news is that there are already some fixtures you can probably use to make a real test (check out this one for an example). The bad news is that that's the only good news.
Then you're probably going to want to look at ObservationQueryBuilder.placeFilterForUser
The text was updated successfully, but these errors were encountered: