Skip to content
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

HC_Manager account issues #245

Open
kkemp85 opened this issue May 16, 2022 · 6 comments
Open

HC_Manager account issues #245

kkemp85 opened this issue May 16, 2022 · 6 comments

Comments

@kkemp85
Copy link
Collaborator

kkemp85 commented May 16, 2022

Got contacted by the Hillsborough County user that the account wasn't showing arch sites. I went in to look at the issue and sure enough, they were no longer seeing arch sites or had access to any. It looks like their account wasn't listed as a land manager account anymore so I went in, maybe wrongly, and deleted it and just made a new land manager account with the same name (the system wouldn't let me make an existing account a land manager account so this was the quick only solution I saw). That worked fine and I could assign the two Hillsborough groups to the account. However, the accessible sites listed aren't correct. They are from all over the state and not just in Hillsborough County (HI). There must be something going on with the geometry filter because they now have access to all these sites they shouldn't but don't have access to the ones they should. We can't have them seeing sites they don't have permission to so I will deactivate arch site access but what can we do @mradamcox to fix this?

image

@kkemp85
Copy link
Collaborator Author

kkemp85 commented Mar 27, 2023

I just got another email from them about this. I did some further looking into the issue. The ELAPP group is working fine, it's the Hillsborough County Parks group that's causing the problem. No sites from any of the parks are showing up when the group is added to the account (or if I go in and add individual county park areas). When I add the Lake area to the group, that's the one that is bringing in all these sites from outside Hillsborough County so something is wrong there too. I opened all the county park areas and all the geometry for each looks correct so I think something else is going on behind the scenes to cause this issue. I'm not sure this is an issue that can be fixed with the ETL module unless we plan on removing these completely and re-adding them with the new module.

@kkemp85
Copy link
Collaborator Author

kkemp85 commented Mar 27, 2023

And a new update - the ELAPP is broken too, there are only 15 sites showing up in the ELAPP, but I show there are over 100.

@mradamcox
Copy link
Contributor

My guess is that it has to do with the spatial join, and the management areas not being properly added to the site resources themselves. It will be solved whenever I can run a full spatial join on the entire database (hopefully very soon!).

@kkemp85
Copy link
Collaborator Author

kkemp85 commented Sep 22, 2023

@mradamcox I forgot about this problem, let's check back in with this one after you have the new LMU tool set up

@kkemp85
Copy link
Collaborator Author

kkemp85 commented Nov 15, 2023

Ok I checked on this. The HC_Manager account can now see all the sites they are supposed to. BUT they can also see sites in Little Manatee River they aren't supposed to (listed below) AND the issue with the Hillsborough County Parks group and the Lake area are still there. I still have to add each individual park/area from the Hillsborough County Parks group to get the sites to show up properly without adding all those random ones from outside Hillsborough. So that's how it's set up for now, the ELAPP group is on there and then all individual parks/areas from the Hillsborough County Parks group are added individually.

Sites they can see but shouldn't (no idea where this issue is coming from - they are properly assign to the SP in Arches and show up in the Little Manatee SP account)

  • HI04597
  • HI04598
  • HI04599
  • HI04600
  • HI04601
  • HI04602
  • HI04603
  • HI04604
  • HI04605
  • HI04606
  • HI04607
  • HI04608

@mradamcox
Copy link
Contributor

Found the issue was with partial overlap in Management Area names. Have appended the object pk to concept values for now, to ensure unique names.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants