Provide a mechanism to allow a given layer to function as a Public layer

[pulsifer]

Nunaliit has a system Layer called Public that allows anyone using the Atlas to add a feature. This can be problematic when you would like to organize features added by users layer. It would be very useful to allow an Atlas builder to assign any layer "Public" functionality (i.e. user can add features without being the Manager of that layer).

[jpfiset]

Amos, what do you think of a 'public_' prefix?

[jpfiset]

With the change above, users can modify features on any public layers. This also includes adding new features to any public layers.

Public layers have a name equal to 'public', or a name that starts with 'public_'. If this is acceptable, then the change above can be retained, as is.

Otherwise, if we settle on a different prefix, some adjustment will be needed.

[ahayes]

Before we decide, what are the distinctions we may want to make in the future? Does it make sense to use a prefix like '+' for open contribution layers? Would we ever want a '_' prefix for hidden layers of some sort? What is the impact of changing a layer from open to closed or vice versa? We might need another chat about this before anyone implements an atlas with this.

Amos Hayes Geomatics and Cartographic Research Centre Carleton University, Canada http://gcrc.carleton.ca ahayes@gcrc.carleton.ca +1.613.520.2600x8179

On 31 July 2013 15:10, Jean-Pierre Fiset notifications@github.com wrote:

With the change above, users can modify features on any public layers. This also includes adding new features to any public layers.

Public layers have a name equal to 'public', or a name that starts with 'public_'. If this is acceptable, then the change above can be retained, as is.

Otherwise, if we settle on a different prefix, some adjustment will be needed.

— Reply to this email directly or view it on GitHubhttps://github.com/GCRC/nunaliit/issues/139#issuecomment-21887565 .

[jpfiset]

Instead of using the name as the indicator of "publicness" for a layer, it is also possible to add a layer as 'public' by adding it to the validate_doc_update. To automate this process, one approach would be to add the public layer in an atlas properties file, run the update command and restart the atlas.

This approach would break the current concept model since the 'atlas editor' requires the cooperation of the 'atlas host' to change the state of a layer. On the plus side, it would allow one to change the status of a layer over time. Also, if we think of new requirements for layers, they could be added to the validation process using the same mechanism.

[ahayes]

Is it something that could be handled by a servlet so that an atlas admin could still accomplish it over the web? Let's discuss offline soon.

Amos Hayes Geomatics and Cartographic Research Centre Carleton University, Canada http://gcrc.carleton.ca ahayes@gcrc.carleton.ca +1.613.520.2600x8179

On 1 August 2013 08:39, Jean-Pierre Fiset notifications@github.com wrote:

Instead of using the name as the indicator of "publicness" for a layer, it is also possible to add a layer as 'public' by adding it to the validate_doc_update. To automate this process, one approach would be to add the public layer in an atlas properties file, run the update command and restart the atlas.

This approach would break the current concept model since the 'atlas editor' requires the cooperation of the 'atlas host' to change the state of a layer. On the plus side, it would allow one to change the status of a layer over time. Also, if we think of new requirements for layers, they could be added to the validation process using the same mechanism.

— Reply to this email directly or view it on GitHubhttps://github.com/GCRC/nunaliit/issues/139#issuecomment-21933336 .

[jpfiset]

As I was reviewing the code, the validate_docupdate has been modified to assume that any layer named with a prefix of 'public' is considered a public layer.