<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
That's what I thought, but not giving the add_layer auth to a group
doesn't affect the group members.<br>
<div class="moz-forward-container"> So first Do I have to make it
work for a single member?<br>
<br>
On the same topic , usually django admin backend has a auth user
menu. It vanished in my geonode installation, there is only the
group auth menu.<br>
Is it the expected behavior ? <br>
<br>
Thanks a lot.<br>
<div class="moz-cite-prefix"> <br>
<br>
<br>
Le 16/06/2015 18:26, Simone Dalmasso a écrit :<br>
</div>
<blockquote
cite="mid:CAAHAC+cuyb9B__9knno5LgctYRHjW6y8NRTNOgWKec3b928FEw@mail.gmail.com"
type="cite">
<div dir="ltr">Hi Hugo,
<div>well this permission is not implemented in GeoNode, you
will need to hack a bit into it and implement checks for it
on the layer upload views and add its support in the client.
The permission itself can then be granted to a group.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2015-06-16 16:13 GMT+02:00 FERRARI
Hugo <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ferrari_hugo@yahoo.fr" target="_blank">ferrari_hugo@yahoo.fr</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hello
world,<br>
in Geonode there are permissions on resources and we can
modify them.<br>
But is there any way to restrict actions for some users ?<br>
I want only few users to be allowed to add new layers in
geonode but apparently the only existing criteria to
permit is authentication.<br>
I'm sure i'm not the first to ask this question.<br>
In auth_permission postgres table we can see that the
"add_layer" permision already exists but it is not
affected to users.<br>
<br>
Thanks for your advices<br>
Hugo FERRARI<br>
<br>
<br>
<br>
<br>
<br>
<br>
Le 09/06/2015 18:50, <a moz-do-not-send="true"
href="mailto:geonode-users-request@lists.osgeo.org"
target="_blank">geonode-users-request@lists.osgeo.org</a>
a écrit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"> Send
geonode-users mailing list submissions to<br>
<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web,
visit<br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users"
rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users</a><br>
or, via email, send a message with subject or body
'help' to<br>
<a moz-do-not-send="true"
href="mailto:geonode-users-request@lists.osgeo.org"
target="_blank">geonode-users-request@lists.osgeo.org</a><br>
<br>
You can reach the person managing the list at<br>
<a moz-do-not-send="true"
href="mailto:geonode-users-owner@lists.osgeo.org"
target="_blank">geonode-users-owner@lists.osgeo.org</a><br>
<br>
When replying, please edit your Subject line so it is
more specific<br>
than "Re: Contents of geonode-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. developpement: Modifying permission behavior and
data<br>
visibility in Geonode (FERRARI Hugo)<br>
2. Re: developpement: Modifying permission behavior
and data<br>
visibility in Geonode (Ariel Nunez)<br>
3. Re: developpement: Modifying permission behavior
and data<br>
visibility in Geonode (Paolo Corti)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 09 Jun 2015 16:56:18 +0400<br>
From: FERRARI Hugo <<a moz-do-not-send="true"
href="mailto:ferrari_hugo@yahoo.fr" target="_blank">ferrari_hugo@yahoo.fr</a>><br>
To: <a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a><br>
Subject: [GeoNode-users] developpement: Modifying
permission behavior<br>
and data visibility in Geonode<br>
Message-ID: <<a moz-do-not-send="true"
href="mailto:5576E272.6090606@yahoo.fr"
target="_blank">5576E272.6090606@yahoo.fr</a>><br>
Content-Type: text/plain; charset=windows-1252;
format=flowed<br>
<br>
Hello everyone,<br>
I have installed a complete geonode instance on a
developpement server.<br>
I want to change thebehaviorofthesoftware to make it
fit the need of<br>
the institution I work for.<br>
So i'm looking for some advices because I didn't manage
to code it yet.<br>
<br>
My aim to separate metada access from the data access.<br>
That is to make all the layers uploaded in geoserver
VISIBLE for all<br>
users (logged or not) but only in the layer-list page ,
not on the<br>
layer-detail page .<br>
If you click on any specific layer in the layer-list (or
document-list<br>
because i want the same behavior for both), you get the
layer detail so<br>
you what will see is:<br>
<br>
- In the case you have the view_resourcebase permission
(who can see it<br>
?), you will see the current template corresponding to<br>
layer_detail.html: both access to datas and metadatas.<br>
- In the other case if you don't have the
view_resourcebase permission,<br>
you 'll only have access to metadatas's ressource (that
means a template<br>
similar to layer_detail.html but Instead of the
geoexplorer frame you<br>
sould have a "permission denied" message, but the
possibility to<br>
retrieve metadata).<br>
<br>
It's quite simple to make all the layers visible in the
layer list,<br>
whoever is logged in (you just have to modify
SKIP_PERMS_FILTERS in<br>
settings.py AND read_list function in module
api/authorisation.py).<br>
but the actual behavior is to catch a 403 http error
when trying to view<br>
the layer detail.<br>
Modifying the 403.html template does not seems to be the
good way to<br>
process.<br>
I don't think it is necessary to modify geonode's
database model because<br>
the view_ressource permission is enough, considering
that viewing the<br>
ressource is equivalent to having access to the data
(even if you can't<br>
download it). There's no need to add a new kind of
permissions, as far<br>
as I can guess.<br>
What is prefered is not throwing a 403 error but just
the<br>
layer_detail.html template modified to get only
metadatas.<br>
<br>
I hope the explanation was clear enough,<br>
Thanks for your advices<br>
Hugo FERRARI<br>
<br>
PS<br>
Does it correspond to the actual geonode developpement
policy ?<br>
Datas and metada are strongly linked in this software.<br>
Could this functionnality be interresting for any other
geonode users?<br>
<br>
<br>
<br>
Le 08/06/2015 23:00, <a moz-do-not-send="true"
href="mailto:geonode-users-request@lists.osgeo.org"
target="_blank">geonode-users-request@lists.osgeo.org</a>
a ?crit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Send geonode-users mailing list submissions to<br>
<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web,
visit<br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users"
rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users</a><br>
or, via email, send a message with subject or body
'help' to<br>
<a moz-do-not-send="true"
href="mailto:geonode-users-request@lists.osgeo.org"
target="_blank">geonode-users-request@lists.osgeo.org</a><br>
<br>
You can reach the person managing the list at<br>
<a moz-do-not-send="true"
href="mailto:geonode-users-owner@lists.osgeo.org"
target="_blank">geonode-users-owner@lists.osgeo.org</a><br>
<br>
When replying, please edit your Subject line so it is
more specific<br>
than "Re: Contents of geonode-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: osgeo module install problem (Simone
Dalmasso)<br>
2. Problems to Translate Geonode - Transifex -
Portuguese<br>
(Brazil) (Davi Custodio)<br>
3. Re: Problems to Translate Geonode - Transifex
- Portuguese<br>
(Brazil) (Julien Collaer)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 7 Jun 2015 21:40:13 +0200<br>
From: Simone Dalmasso <<a moz-do-not-send="true"
href="mailto:simone.dalmasso@gmail.com"
target="_blank">simone.dalmasso@gmail.com</a>><br>
To: Vicente <<a moz-do-not-send="true"
href="mailto:deluca.vicente@gmail.com"
target="_blank">deluca.vicente@gmail.com</a>><br>
Cc: geonode-users <<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a>><br>
Subject: Re: [GeoNode-users] osgeo module install
problem<br>
Message-ID:<br>
<CAAHAC+cU9GgbBUe-ocH4GJZ1PaXEZDrY5W=<a
moz-do-not-send="true"
href="mailto:ZCsTzSUSx5ymVvA@mail.gmail.com"
target="_blank">ZCsTzSUSx5ymVvA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi, you are missing the gdal python bindings, a "pip
install gdal" should<br>
fix it.<br>
<br>
Hope it helps, ciao<br>
<br>
2015-06-07 17:59 GMT+02:00 Vicente <<a
moz-do-not-send="true"
href="mailto:deluca.vicente@gmail.com"
target="_blank">deluca.vicente@gmail.com</a>>:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Good afternoon,<br>
If I run the following line from my command line,
the answer is successful<br>
<br>
$ sudo apt-get -y install libgdal1h libgdal-dev
python-gdal<br>
<br>
But if I run from the session virtualenv, the answer
is No module named<br>
osgeo.<br>
<br>
I have just added the following session variables in
my .bashrc:<br>
export VIRTUALENVWRAPPER_PYTHON = / usr / bin /
python<br>
export WORKON_HOME = ~ / .venvs<br>
source /usr/local/bin/virtualenvwrapper.sh<br>
export PIP_DOWNLOAD_CACHE = $ HOME / .pip-downloads<br>
<br>
Both session with virtualenv or outside, the python
to run is the same,<br>
Python 2.7.6 (default, Mar 22 2014, 22:59:56)<br>
<br>
The result is that I can not run because there is
paver start the osgeo<br>
module from within the session obviously.<br>
<br>
Thanks!<br>
<br>
--<br>
<br>
[image: MANTA] <<a moz-do-not-send="true"
href="http://www.estudiomanta.com/"
rel="noreferrer" target="_blank">http://www.estudiomanta.com/</a>><br>
<br>
<br>
<br>
Vicente Deluca<br>
<br>
*<a moz-do-not-send="true"
href="tel:%2B54%2011%206091%204579"
value="+541160914579" target="_blank">+54 11 6091
4579</a> <%2B54%2011%206091%204579>*<br>
<br>
<br>
_______________________________________________<br>
geonode-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users"
rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users</a><br>
<br>
<br>
</blockquote>
</blockquote>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 9 Jun 2015 09:01:34 -0500<br>
From: Ariel Nunez <<a moz-do-not-send="true"
href="mailto:ingenieroariel@gmail.com" target="_blank">ingenieroariel@gmail.com</a>><br>
To: FERRARI Hugo <<a moz-do-not-send="true"
href="mailto:ferrari_hugo@yahoo.fr" target="_blank">ferrari_hugo@yahoo.fr</a>><br>
Cc: "<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a>"
<<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a>><br>
Subject: Re: [GeoNode-users] developpement: Modifying
permission<br>
behavior and data visibility in Geonode<br>
Message-ID:<br>
<<a moz-do-not-send="true"
href="mailto:CALh6R-QDnFhFPgQdejPp0Kuh5NABLExo7ONaQWjhyb2hk3chEw@mail.gmail.com"
target="_blank">CALh6R-QDnFhFPgQdejPp0Kuh5NABLExo7ONaQWjhyb2hk3chEw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hugo,<br>
<br>
Based on what I understand, the best path forward is to
have a<br>
view_metadata permission that you use to enforce the
behavior you want.<br>
Assigning a new meaning to the existing permission may
be problematic for<br>
other users with different needs (for example where
metadata is sensitive<br>
information).<br>
<br>
The place where we want to get to, is to allow uploaders
to restrict any<br>
actions they want, but give the end user buttons to
request permissions (to<br>
view if they cannot view, to download if they can only
view, to edit if the<br>
can only download) to encourage a conversation between
uploaders and users<br>
and provide a workflow to allow access to information
when it is needed.<br>
<br>
The changes you make would be good candidates for
inclusion in the main<br>
version of GeoNode so others can benefit in the future.
Hopefully others<br>
(Paolo?) can chime in with more specific feedback.<br>
<br>
Best,<br>
Ariel.<br>
<br>
On Tue, Jun 9, 2015 at 7:56 AM, FERRARI Hugo <<a
moz-do-not-send="true"
href="mailto:ferrari_hugo@yahoo.fr" target="_blank">ferrari_hugo@yahoo.fr</a>>
wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello everyone,<br>
I have installed a complete geonode instance on a
developpement server.<br>
I want to change thebehaviorofthesoftware to make it
fit the need of the<br>
institution I work for.<br>
So i'm looking for some advices because I didn't
manage to code it yet.<br>
<br>
My aim to separate metada access from the data access.<br>
That is to make all the layers uploaded in geoserver
VISIBLE for all<br>
users (logged or not) but only in the layer-list page
, not on the<br>
layer-detail page .<br>
If you click on any specific layer in the layer-list
(or document-list<br>
because i want the same behavior for both), you get
the layer detail so you<br>
what will see is:<br>
<br>
- In the case you have the view_resourcebase
permission (who can see it<br>
?), you will see the current template corresponding to
layer_detail.html:<br>
both access to datas and metadatas.<br>
- In the other case if you don't have the
view_resourcebase permission,<br>
you 'll only have access to metadatas's ressource
(that means a template<br>
similar to layer_detail.html but Instead of the
geoexplorer frame you sould<br>
have a "permission denied" message, but the
possibility to retrieve<br>
metadata).<br>
<br>
It's quite simple to make all the layers visible in
the layer list,<br>
whoever is logged in (you just have to modify
SKIP_PERMS_FILTERS in<br>
settings.py AND read_list function in module
api/authorisation.py).<br>
but the actual behavior is to catch a 403 http error
when trying to view<br>
the layer detail.<br>
Modifying the 403.html template does not seems to be
the good way to<br>
process.<br>
I don't think it is necessary to modify geonode's
database model because<br>
the view_ressource permission is enough, considering
that viewing the<br>
ressource is equivalent to having access to the data
(even if you can't<br>
download it). There's no need to add a new kind of
permissions, as far as I<br>
can guess.<br>
What is prefered is not throwing a 403 error but just
the<br>
layer_detail.html template modified to get only
metadatas.<br>
<br>
I hope the explanation was clear enough,<br>
Thanks for your advices<br>
Hugo FERRARI<br>
<br>
PS<br>
Does it correspond to the actual geonode developpement
policy ?<br>
Datas and metada are strongly linked in this software.<br>
Could this functionnality be interresting for any
other geonode users?<br>
<br>
<br>
<br>
Le 08/06/2015 23:00, <a moz-do-not-send="true"
href="mailto:geonode-users-request@lists.osgeo.org"
target="_blank">geonode-users-request@lists.osgeo.org</a>
a ?crit :<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Send geonode-users mailing list submissions to<br>
<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web,
visit<br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users"
rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users</a><br>
or, via email, send a message with subject or body
'help' to<br>
<a moz-do-not-send="true"
href="mailto:geonode-users-request@lists.osgeo.org"
target="_blank">geonode-users-request@lists.osgeo.org</a><br>
<br>
You can reach the person managing the list at<br>
<a moz-do-not-send="true"
href="mailto:geonode-users-owner@lists.osgeo.org"
target="_blank">geonode-users-owner@lists.osgeo.org</a><br>
<br>
When replying, please edit your Subject line so it
is more specific<br>
than "Re: Contents of geonode-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: osgeo module install problem (Simone
Dalmasso)<br>
2. Problems to Translate Geonode - Transifex -
Portuguese<br>
(Brazil) (Davi Custodio)<br>
3. Re: Problems to Translate Geonode -
Transifex - Portuguese<br>
(Brazil) (Julien Collaer)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 7 Jun 2015 21:40:13 +0200<br>
From: Simone Dalmasso <<a moz-do-not-send="true"
href="mailto:simone.dalmasso@gmail.com"
target="_blank">simone.dalmasso@gmail.com</a>><br>
To: Vicente <<a moz-do-not-send="true"
href="mailto:deluca.vicente@gmail.com"
target="_blank">deluca.vicente@gmail.com</a>><br>
Cc: geonode-users <<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a>><br>
Subject: Re: [GeoNode-users] osgeo module install
problem<br>
Message-ID:<br>
<CAAHAC+cU9GgbBUe-ocH4GJZ1PaXEZDrY5W=<br>
<a moz-do-not-send="true"
href="mailto:ZCsTzSUSx5ymVvA@mail.gmail.com"
target="_blank">ZCsTzSUSx5ymVvA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi, you are missing the gdal python bindings, a "pip
install gdal" should<br>
fix it.<br>
<br>
Hope it helps, ciao<br>
<br>
2015-06-07 17:59 GMT+02:00 Vicente <<a
moz-do-not-send="true"
href="mailto:deluca.vicente@gmail.com"
target="_blank">deluca.vicente@gmail.com</a>>:<br>
<br>
Good afternoon,<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
If I run the following line from my command line,
the answer is<br>
successful<br>
<br>
$ sudo apt-get -y install libgdal1h libgdal-dev
python-gdal<br>
<br>
But if I run from the session virtualenv, the
answer is No module named<br>
osgeo.<br>
<br>
I have just added the following session variables
in my .bashrc:<br>
export VIRTUALENVWRAPPER_PYTHON = / usr / bin /
python<br>
export WORKON_HOME = ~ / .venvs<br>
source /usr/local/bin/virtualenvwrapper.sh<br>
export PIP_DOWNLOAD_CACHE = $ HOME /
.pip-downloads<br>
<br>
Both session with virtualenv or outside, the
python to run is the same,<br>
Python 2.7.6 (default, Mar 22 2014, 22:59:56)<br>
<br>
The result is that I can not run because there is
paver start the osgeo<br>
module from within the session obviously.<br>
<br>
Thanks!<br>
<br>
--<br>
<br>
[image: MANTA] <<a moz-do-not-send="true"
href="http://www.estudiomanta.com/"
rel="noreferrer" target="_blank">http://www.estudiomanta.com/</a>><br>
<br>
<br>
<br>
Vicente Deluca<br>
<br>
*<a moz-do-not-send="true"
href="tel:%2B54%2011%206091%204579"
value="+541160914579" target="_blank">+54 11
6091 4579</a> <%2B54%2011%206091%204579>*<br>
<br>
<br>
_______________________________________________<br>
geonode-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users"
rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users</a><br>
<br>
<br>
<br>
</blockquote>
</blockquote>
_______________________________________________<br>
geonode-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users"
rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users</a><br>
<br>
</blockquote>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a moz-do-not-send="true"
href="http://lists.osgeo.org/pipermail/geonode-users/attachments/20150609/4dbe42d3/attachment-0001.html"
rel="noreferrer" target="_blank">http://lists.osgeo.org/pipermail/geonode-users/attachments/20150609/4dbe42d3/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 9 Jun 2015 16:50:01 +0200<br>
From: Paolo Corti <<a moz-do-not-send="true"
href="mailto:pcorti@gmail.com" target="_blank">pcorti@gmail.com</a>><br>
To: Ariel Nunez <<a moz-do-not-send="true"
href="mailto:ingenieroariel@gmail.com" target="_blank">ingenieroariel@gmail.com</a>><br>
Cc: FERRARI Hugo <<a moz-do-not-send="true"
href="mailto:ferrari_hugo@yahoo.fr" target="_blank">ferrari_hugo@yahoo.fr</a>>,<br>
"<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a>"
<<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a>><br>
Subject: Re: [GeoNode-users] developpement: Modifying
permission<br>
behavior and data visibility in Geonode<br>
Message-ID:<br>
<<a moz-do-not-send="true"
href="mailto:CAHXrU-JBaUUQUBz7BjsNuTkmOpOSLB7rxAaXEt3Qsn1TmKmvqw@mail.gmail.com"
target="_blank">CAHXrU-JBaUUQUBz7BjsNuTkmOpOSLB7rxAaXEt3Qsn1TmKmvqw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Yes, Ariel is totally right.<br>
Currently we don't have a specific permission for
viewing metadata.<br>
This is implicit with the view_resourcebase permission
that gives<br>
access to the data and metadata at the same time.<br>
As suggested by Ariel you may consider to add a new
django guardian<br>
permission at the resource base model, like it has been
done here [1]<br>
and then have your GeoNode instance behaved according to
it in views,<br>
templates and javascript.<br>
I don't think there is an easy way to avoid forking
GeoNode and<br>
customize the beahviour in your GeoNode project, though
it may be not<br>
impossible and this would keep your instance easily
updateable with<br>
mainstream code.<br>
Even better, as Ariel suggested, you may though fork it
and send a PR<br>
as it could be useful for others as well.<br>
regards<br>
p<br>
<br>
[1] <a moz-do-not-send="true"
href="https://github.com/GeoNode/geonode/blob/master/geonode/base/models.py#L648"
rel="noreferrer" target="_blank">https://github.com/GeoNode/geonode/blob/master/geonode/base/models.py#L648</a><br>
<br>
<br>
On Tue, Jun 9, 2015 at 4:01 PM, Ariel Nunez <<a
moz-do-not-send="true"
href="mailto:ingenieroariel@gmail.com" target="_blank">ingenieroariel@gmail.com</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hugo,<br>
<br>
Based on what I understand, the best path forward is
to have a view_metadata<br>
permission that you use to enforce the behavior you
want. Assigning a new<br>
meaning to the existing permission may be problematic
for other users with<br>
different needs (for example where metadata is
sensitive information).<br>
<br>
The place where we want to get to, is to allow
uploaders to restrict any<br>
actions they want, but give the end user buttons to
request permissions (to<br>
view if they cannot view, to download if they can only
view, to edit if the<br>
can only download) to encourage a conversation between
uploaders and users<br>
and provide a workflow to allow access to information
when it is needed.<br>
<br>
The changes you make would be good candidates for
inclusion in the main<br>
version of GeoNode so others can benefit in the
future. Hopefully others<br>
(Paolo?) can chime in with more specific feedback.<br>
<br>
Best,<br>
Ariel.<br>
<br>
On Tue, Jun 9, 2015 at 7:56 AM, FERRARI Hugo <<a
moz-do-not-send="true"
href="mailto:ferrari_hugo@yahoo.fr" target="_blank">ferrari_hugo@yahoo.fr</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello everyone,<br>
I have installed a complete geonode instance on a
developpement server.<br>
I want to change thebehaviorofthesoftware to make
it fit the need of the<br>
institution I work for.<br>
So i'm looking for some advices because I didn't
manage to code it yet.<br>
<br>
My aim to separate metada access from the data
access.<br>
That is to make all the layers uploaded in
geoserver VISIBLE for all<br>
users (logged or not) but only in the layer-list
page , not on the<br>
layer-detail page .<br>
If you click on any specific layer in the layer-list
(or document-list<br>
because i want the same behavior for both), you get
the layer detail so you<br>
what will see is:<br>
<br>
- In the case you have the view_resourcebase
permission (who can see it<br>
?), you will see the current template corresponding
to layer_detail.html:<br>
both access to datas and metadatas.<br>
- In the other case if you don't have the
view_resourcebase permission,<br>
you 'll only have access to metadatas's ressource
(that means a template<br>
similar to layer_detail.html but Instead of the
geoexplorer frame you sould<br>
have a "permission denied" message, but the
possibility to retrieve<br>
metadata).<br>
<br>
It's quite simple to make all the layers visible in
the layer list,<br>
whoever is logged in (you just have to modify
SKIP_PERMS_FILTERS in<br>
settings.py AND read_list function in module
api/authorisation.py).<br>
but the actual behavior is to catch a 403 http error
when trying to view<br>
the layer detail.<br>
Modifying the 403.html template does not seems to be
the good way to<br>
process.<br>
I don't think it is necessary to modify geonode's
database model because<br>
the view_ressource permission is enough,
considering that viewing the<br>
ressource is equivalent to having access to the data
(even if you can't<br>
download it). There's no need to add a new kind of
permissions, as far as I<br>
can guess.<br>
What is prefered is not throwing a 403 error but
just the<br>
layer_detail.html template modified to get only
metadatas.<br>
<br>
I hope the explanation was clear enough,<br>
Thanks for your advices<br>
Hugo FERRARI<br>
<br>
PS<br>
Does it correspond to the actual geonode
developpement policy ?<br>
Datas and metada are strongly linked in this
software.<br>
Could this functionnality be interresting for any
other geonode users?<br>
<br>
<br>
<br>
Le 08/06/2015 23:00, <a moz-do-not-send="true"
href="mailto:geonode-users-request@lists.osgeo.org"
target="_blank">geonode-users-request@lists.osgeo.org</a>
a ?crit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Send geonode-users mailing list submissions to<br>
<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide
Web, visit<br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users"
rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users</a><br>
or, via email, send a message with subject or body
'help' to<br>
<a moz-do-not-send="true"
href="mailto:geonode-users-request@lists.osgeo.org"
target="_blank">geonode-users-request@lists.osgeo.org</a><br>
<br>
You can reach the person managing the list at<br>
<a moz-do-not-send="true"
href="mailto:geonode-users-owner@lists.osgeo.org"
target="_blank">geonode-users-owner@lists.osgeo.org</a><br>
<br>
When replying, please edit your Subject line so it
is more specific<br>
than "Re: Contents of geonode-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: osgeo module install problem (Simone
Dalmasso)<br>
2. Problems to Translate Geonode - Transifex
- Portuguese<br>
(Brazil) (Davi Custodio)<br>
3. Re: Problems to Translate Geonode -
Transifex - Portuguese<br>
(Brazil) (Julien Collaer)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 7 Jun 2015 21:40:13 +0200<br>
From: Simone Dalmasso <<a
moz-do-not-send="true"
href="mailto:simone.dalmasso@gmail.com"
target="_blank">simone.dalmasso@gmail.com</a>><br>
To: Vicente <<a moz-do-not-send="true"
href="mailto:deluca.vicente@gmail.com"
target="_blank">deluca.vicente@gmail.com</a>><br>
Cc: geonode-users <<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a>><br>
Subject: Re: [GeoNode-users] osgeo module install
problem<br>
Message-ID:<br>
<br>
<CAAHAC+cU9GgbBUe-ocH4GJZ1PaXEZDrY5W=<a
moz-do-not-send="true"
href="mailto:ZCsTzSUSx5ymVvA@mail.gmail.com"
target="_blank">ZCsTzSUSx5ymVvA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi, you are missing the gdal python bindings, a
"pip install gdal" should<br>
fix it.<br>
<br>
Hope it helps, ciao<br>
<br>
2015-06-07 17:59 GMT+02:00 Vicente <<a
moz-do-not-send="true"
href="mailto:deluca.vicente@gmail.com"
target="_blank">deluca.vicente@gmail.com</a>>:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex"> Good afternoon,<br>
If I run the following line from my command
line, the answer is<br>
successful<br>
<br>
$ sudo apt-get -y install libgdal1h libgdal-dev
python-gdal<br>
<br>
But if I run from the session virtualenv, the
answer is No module named<br>
osgeo.<br>
<br>
I have just added the following session
variables in my .bashrc:<br>
export VIRTUALENVWRAPPER_PYTHON = / usr / bin /
python<br>
export WORKON_HOME = ~ / .venvs<br>
source /usr/local/bin/virtualenvwrapper.sh<br>
export PIP_DOWNLOAD_CACHE = $ HOME /
.pip-downloads<br>
<br>
Both session with virtualenv or outside, the
python to run is the same,<br>
Python 2.7.6 (default, Mar 22 2014, 22:59:56)<br>
<br>
The result is that I can not run because there
is paver start the osgeo<br>
module from within the session obviously.<br>
<br>
Thanks!<br>
<br>
--<br>
<br>
[image: MANTA] <<a moz-do-not-send="true"
href="http://www.estudiomanta.com/"
rel="noreferrer" target="_blank">http://www.estudiomanta.com/</a>><br>
<br>
<br>
<br>
Vicente Deluca<br>
<br>
*<a moz-do-not-send="true"
href="tel:%2B54%2011%206091%204579"
value="+541160914579" target="_blank">+54 11
6091 4579</a>
<%2B54%2011%206091%204579>*<br>
<br>
<br>
_______________________________________________<br>
geonode-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users"
rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users</a><br>
<br>
<br>
</blockquote>
</blockquote>
_______________________________________________<br>
geonode-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users"
rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users</a><br>
</blockquote>
<br>
<br>
_______________________________________________<br>
geonode-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users"
rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users</a><br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
_______________________________________________<br>
geonode-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:geonode-users@lists.osgeo.org"
target="_blank">geonode-users@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users"
rel="noreferrer" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">Simone </div>
</div>
</blockquote>
<br>
<br>
</div>
<br>
</body>
</html>