[GeoNode-users] Understanding group permissions in GeoNode

[Daniel Victoria]

Hi Simone, Seno,

Thanks for the info. We will try to implement the changes here. Is there
some documentation showing which parts of the code needs to be changed?

Cheers
Daniel

On Thu, Sep 24, 2015 at 6:58 AM, Simone Dalmasso <simone.dalmasso at gmail.com>
wrote:

> Thanks Seno,
>
> just to add that the default anonymous permissions (and the checkbox
> behavior) can be controlled by these settings
> https://github.com/GeoNode/geonode/blob/master/geonode/settings.py#L401
>
> 2015-09-24 9:04 GMT+02:00 Seno Adiwicaksono <senoadiw at gmail.com>:
>
>> Hi Daniel,
>>
>> I sort of got this flow working. What was done is to make sure that the
>> approving group (call it GroupApproval) is given all the group permissions
>> in the layer upload page, I set it through javascript to fill the
>> permissions textbox with GroupApproval. Also it is key to make sure the
>> Anyone (view and download) checkboxes are unchecked. Once the user has
>> successfully uploaded the layer, an email notification is sent to members
>> of GroupApproval. Since the Anyone view permission is unchecked, the layer
>> will not show up in the layers list even though it's published. Then the
>> GroupApproval member can visit the new layer from the link in the email,
>> review it, and finally check the Anyone view and download permissions so it
>> is accessible by the public.
>>
>> Hope this helps!
>>
>> Regards,
>>
>> SN
>>
>> On Thu, Sep 24, 2015 at 1:19 PM, Simone Dalmasso <
>> simone.dalmasso at gmail.com> wrote:
>>
>>> Hi Daniel,
>>> what you want to achieve cannot be done with standard GeoNode as, by
>>> default, a user that uploads data is also the owner and can publish and
>>> modify it. You would have to modify the standard permissions (easy
>>> setting), the UI to remove the public flags and not grant the
>>> "change_resourcebase_permissions" permission to the users that should not
>>> be able to publish.
>>> Then you have to add the notifications system to the group you need for
>>> "layer_uploaded".
>>>
>>> About the permissions, don't consider the ones in the "admin panel" as
>>> they contain also some django internals that we don't use. the GeoNode
>>> permissions are the ones listed in the permissions widget:
>>>
>>>
>>>
>>> 2015-09-23 21:15 GMT+02:00 Daniel Victoria <daniel.victoria at gmail.com>:
>>>
>>>> Hi list,
>>>>
>>>> We'd like to create some groups in GeoNode similar to what Seno
>>>> describes bellow. One group that can upload data and fill the metadata but
>>>> not make it public. And a second group that will review, correct the
>>>> metadata and make it public. Is this done using only the group permissions?
>>>> Or are there some other things that need to be changed?
>>>>
>>>> Also, looking at the group permissions in the administration panel, I
>>>> got lost. Is there some place that describes what each of the permissions
>>>> is for? Some are quite self-describing but, what is the difference between:
>>>> a) can add layer vs. can add layer file
>>>> b) can add upload vs. can add upload file
>>>>
>>>> Cheers
>>>> Daniel
>>>>
>>>> On Mon, Sep 7, 2015 at 9:25 AM, Seno Adiwicaksono <senoadiw at gmail.com>
>>>> wrote:
>>>>
>>>>> Dear all,
>>>>>
>>>>> I have a specific use case with regards the django-notification used
>>>>> in GeoNode. The requirements are to only send a layer_created notice to
>>>>> specific group managers. The group managers will then review and publish
>>>>> the uploaded layer. I put a call to notification.send(managers,
>>>>> 'layer_created', notif_ctx) after a new layer object is saved, which then
>>>>> sends the layer_created email to the managers. However they receive 2
>>>>> layer_created emails. I suppose the first one is from my manual call and
>>>>> the second one is because the managers are subscribed to layer_created in
>>>>> the notification settings. I then uncheck the setting and tried uploading
>>>>> another layer expecting to receive only 1 email this time, however none was
>>>>> received. I enabled the settings again and 2 emails were delivered. I find
>>>>> it strange that the saved settings would also affect my manual call.
>>>>>
>>>>> So my question is where in GeoNode's code can I look to disable
>>>>> sending the 2nd email?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> SN
>>>>>
>>>>> _______________________________________________
>>>>> geonode-users mailing list
>>>>> geonode-users at lists.osgeo.org
>>>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> geonode-users mailing list
>>>> geonode-users at lists.osgeo.org
>>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users
>>>>
>>>>
>>>
>>>
>>> --
>>> Simone
>>>
>>> _______________________________________________
>>> geonode-users mailing list
>>> geonode-users at lists.osgeo.org
>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users
>>>
>>>
>>
>
>
> --
> Simone
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20150924/a7b3519e/attachment.html>