{"action":"created","issue":{"url":"https://api.github.com/repos/archesproject/arches/issues/2492","repository_url":"https://api.github.com/repos/archesproject/arches","labels_url":"https://api.github.com/repos/archesproject/arches/issues/2492/labels{/name}","comments_url":"https://api.github.com/repos/archesproject/arches/issues/2492/comments","events_url":"https://api.github.com/repos/archesproject/arches/issues/2492/events","html_url":"https://github.com/archesproject/arches/issues/2492","id":262575050,"number":2492,"title":"Restricting Access To A Geospatial Node Still Allows General Access To Coordinates","user":{"login":"mradamcox","id":10427268,"avatar_url":"https://avatars3.githubusercontent.com/u/10427268?v=4","gravatar_id":"","url":"https://api.github.com/users/mradamcox","html_url":"https://github.com/mradamcox","followers_url":"https://api.github.com/users/mradamcox/followers","following_url":"https://api.github.com/users/mradamcox/following{/other_user}","gists_url":"https://api.github.com/users/mradamcox/gists{/gist_id}","starred_url":"https://api.github.com/users/mradamcox/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mradamcox/subscriptions","organizations_url":"https://api.github.com/users/mradamcox/orgs","repos_url":"https://api.github.com/users/mradamcox/repos","events_url":"https://api.github.com/users/mradamcox/events{/privacy}","received_events_url":"https://api.github.com/users/mradamcox/received_events","type":"User","site_admin":false},"labels":[{"id":742548840,"url":"https://api.github.com/repos/archesproject/arches/labels/Roadmap:%20DISCO%20-%20Task%208","name":"Roadmap: DISCO - Task 8","color":"c5def5","default":false},{"id":309906303,"url":"https://api.github.com/repos/archesproject/arches/labels/Type:%20Bug","name":"Type: Bug","color":"fc2929","default":false}],"state":"closed","locked":false,"assignee":{"login":"adamlodge","id":9683819,"avatar_url":"https://avatars1.githubusercontent.com/u/9683819?v=4","gravatar_id":"","url":"https://api.github.com/users/adamlodge","html_url":"https://github.com/adamlodge","followers_url":"https://api.github.com/users/adamlodge/followers","following_url":"https://api.github.com/users/adamlodge/following{/other_user}","gists_url":"https://api.github.com/users/adamlodge/gists{/gist_id}","starred_url":"https://api.github.com/users/adamlodge/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adamlodge/subscriptions","organizations_url":"https://api.github.com/users/adamlodge/orgs","repos_url":"https://api.github.com/users/adamlodge/repos","events_url":"https://api.github.com/users/adamlodge/events{/privacy}","received_events_url":"https://api.github.com/users/adamlodge/received_events","type":"User","site_admin":false},"assignees":[{"login":"adamlodge","id":9683819,"avatar_url":"https://avatars1.githubusercontent.com/u/9683819?v=4","gravatar_id":"","url":"https://api.github.com/users/adamlodge","html_url":"https://github.com/adamlodge","followers_url":"https://api.github.com/users/adamlodge/followers","following_url":"https://api.github.com/users/adamlodge/following{/other_user}","gists_url":"https://api.github.com/users/adamlodge/gists{/gist_id}","starred_url":"https://api.github.com/users/adamlodge/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adamlodge/subscriptions","organizations_url":"https://api.github.com/users/adamlodge/orgs","repos_url":"https://api.github.com/users/adamlodge/repos","events_url":"https://api.github.com/users/adamlodge/events{/privacy}","received_events_url":"https://api.github.com/users/adamlodge/received_events","type":"User","site_admin":false}],"milestone":null,"comments":2,"created_at":"2017-10-03T20:30:56Z","updated_at":"2018-05-24T19:19:30Z","closed_at":"2018-05-24T19:19:29Z","author_association":"COLLABORATOR","body":"### Bug Report - from @mradamcox \r\nCurrently, a user/user group can be restricted from seeing a Geospatial node, just as any other node may be restricted. Doing so successfully hides that node's geospatial overlay layer in the search view from the user.\r\n\r\nHowever, these nodes are still used in the creation of the \"search results overlay\" hex bins. This means that in some situations archaeological site locations could be very much exposed (e.g. a small project area with small hex bins).\r\n\r\nFurther, if these Archaeological Sites show up in search results, which is a legitimate possibility if guests are allowed Read access to non-spatial attributes, the map will still automatically zoom to the coordinates. In a database with only a few archaeological sites, or a number of sites that are in a very tight cluster, the location of these sites would be pretty clearly revealed.\r\n\r\n#### Definition of Done\r\nIf a geospatial coordinate node is restricted for a user/user group, that node should actually be hidden from that user/user group. This must include (though may not be limited to)\r\n\r\n- [ ] the creation of the search results overlay\r\n- [ ] the automatic search results zoom function\r\n\r\n#### system info\r\nArches 4.0.0\r\n\r\n### Bug Report - from @ajwuthrich\r\n<!--- By fully explaining what you are encountering, you can help us understand and reproduce the issue.  -->\r\n\r\n#### Expected Behavior\r\nWhen a user or group is put on no access to a Resource Model's location card, using that model's search filter should not cause the data to affect the map or its orientation.\r\n\r\n#### Current Behavior\r\nWhen a user or group is denied access to a Resource Model's location card, the map still reacts to a user search like they have access to the data. The only difference is that the location information does not show up on the map. \r\n\r\nFor example, if the administrator was to put the location card of HER Find Models on 'No Access' for a specific user or group, the group would not be able to view the data points on the Map Search. However, if the filter is activated, the map search still zooms in automatically to show the user where the Find Model locations are.\r\n\r\n#### Steps to Reproduce (for bugs)\r\n1. Open Arches 4.1.1 in browser\r\n2. Disable 'read' permissions on a Resource Model's location card\r\n3. Navigate to Map search and apply that model's search filter\r\n4. Observe error listed above\r\n\r\nhttp://recordit.co/8PL9Ig1aRd\r\nhttp://recordit.co/inQWMRyBdv\r\n\r\n#### Your Arches Information\r\n* Version used: 4.1.1\r\n* Browser Name and version: Chrome, Safari, Firefox, IE11\r\n* Operating System and version (desktop or mobile): Mac OS, Windows 10\r\n"},"comment":{"url":"https://api.github.com/repos/archesproject/arches/issues/comments/391829124","html_url":"https://github.com/archesproject/arches/issues/2492#issuecomment-391829124","issue_url":"https://api.github.com/repos/archesproject/arches/issues/2492","id":391829124,"user":{"login":"adamlodge","id":9683819,"avatar_url":"https://avatars1.githubusercontent.com/u/9683819?v=4","gravatar_id":"","url":"https://api.github.com/users/adamlodge","html_url":"https://github.com/adamlodge","followers_url":"https://api.github.com/users/adamlodge/followers","following_url":"https://api.github.com/users/adamlodge/following{/other_user}","gists_url":"https://api.github.com/users/adamlodge/gists{/gist_id}","starred_url":"https://api.github.com/users/adamlodge/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adamlodge/subscriptions","organizations_url":"https://api.github.com/users/adamlodge/orgs","repos_url":"https://api.github.com/users/adamlodge/repos","events_url":"https://api.github.com/users/adamlodge/events{/privacy}","received_events_url":"https://api.github.com/users/adamlodge/received_events","type":"User","site_admin":false},"created_at":"2018-05-24T19:19:30Z","updated_at":"2018-05-24T19:19:30Z","author_association":"CONTRIBUTOR","body":"The behavior I saw in the comment above was a result of the HER Place node being set to \"no access\".  That (lack of) privilege flows downstream to the child nodes within the card container regardless of what privs are assigned to the child nodes.\n\nMeets requirements as it relates to original intent of the ticket regarding access to spatial information.  Closing ticket."}}
{"actor":{"display_login":"adamlodge"}}