Open fmadelung opened 6 years ago
There is currently a deficiency in the MPCM rest service that prevents filtering the table listing on request. Due to the length of time it would take to query every single layer to filter, this will not be possible at the current time (once mpcm's rest service is updated we can update this too). The layer selection has been updated to prevent users from loading secure layers (they can't be at all), and they will be alerted when they attempt to do so.
Note again, that there is nothing we can do to prevent this if someone exports their application and adds the secure layer string manually.
This is related to https://github.com/bcgov/smk/issues/81
As an author, I can still see Archaeology Sites as a layer I can try to add. I do have permission to see the layer in alternative platforms (IMF2, etc).
As described above, until the MPCM rest service is updated to show a layers workspace, or allow for us to filter on request, it will be extremely time-consuming to render a list with all secure layers removed. We would have to pre-load all MPCM layers (not just the list view), strip out any that aren't secure, and return that to the user on request.
So, our options here are: 1.) Wait for an MPCM rest service change. The Admin UI will show secure layers, but it currently will not let you add them. 2.) Prebuild the list on the server every day. That should negate the performance hit from doing it whenever a client requests the MPCM catalog.
Option #1 is in the queue for MPCM v1.4. Should ask Chris B as to its status. Moving this to icebox for now.
Layers that are "secure" should not be shown in the layer list as it is a public environment.
Layers that are "secure" can be added to the layer list but are not shown in the map viewer. When viewing the layer list in the Map Viewer, click the arrow for the layer (to see the symbology). Instead of showing the symbology, the layer says "requesting"