[ckan-dev] Authorisation - making datasets public

Tue Jun 10 05:22:59 UTC 2014

Hi Aaron,

As far as I can see, it's a bug in the documentation. Everyone who has
permissions to update the datasets (admin and editors) can change the
private/public flag.

At the moment, I don't know of any new features that will change that behavior.
If you would like to see that happen, it might be worth filing a bug against
the ideas and roadmap repository[1].

[1]: https://github.com/ckan/ideas-and-roadmap/

On Mon, Jun 09, 2014 at 03:37:18AM +0000, Aaron McGlinchy wrote:
> Thanks Rodrigo,
>                 What you describe sounds like it would work for us.
>
> However, I'd like to bump this for a response from the CKAN team as well - is the original issue described an error in the documentation (ie.  Docs should say editor can make public/private, not just admin)
> OR
> is this a change that is forthcoming in version 2.3 (public/private setting ablity will be limited to Admins)?
>
> Cheers
> Aaron
> ------------------------------
>
> Message: 2
> Date: Wed, 28 May 2014 09:48:35 -0400
> From: Rodrigo Parra <rodpar07 at gmail.com>
> To: CKAN Development Discussions <ckan-dev at lists.okfn.org>
> Subject: Re: [ckan-dev] Authorisation - making datasets public
> Message-ID:
>         <CAFifmxkDf9kV6rS--=egwD7LAFD2wOz4-d+_OjsZwcm-3PW54g at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Aaron,
>
> I came across the same issue in the past week, I also needed making datasets public to be an admin-only feature.
> Currently, I think both editors and admins of an organization can create public datasets. So I've implemented a this feature as part of a CKAN extension I'm developing.
>
> What I did was:
>
>    - Remove the visibility select field from the dataset form. (for all
>    users but the sysadmin).
>    - Create all datasets as private (except if the dataset was created by
>    the sysadmin, in which case the chosen visibility is used).
>    - Show the visibility select field in the dataset edit form if the user
>    is an organization admin (or the sysadmin).
>
> So basically, users create private datasets and admins "approve and publish" the datasets ("Manage" -> set visibility to public).
> This is the github commit that includes these changes:
>  https://github.com/rparrapy/ckanext-datospy/commit/92fa82141d62e96040322a7e06985a97774f5774<https://github.com/rparrapy/ckanext-datospy/commit/92fa82141d62e96040322a7e06985a97774f5774>
>
>
> And here's a link to some documentation I've written about it:
> http://datosparaguay.org/xwiki/bin/view/herramientas/ckan_autorizacion
> I'm sorry but:
>
>    - It is in spanish. Google translated version here: http://goo.gl/1dGsJ9
>    - It references some documents that might not be publicly available yet.
>
>
> Hope this helps. Regards,
> Rodrigo
>
>
> 2014-05-27 21:10 GMT-04:00 Aaron McGlinchy <
> McGlinchyA at landcareresearch.co.nz>:
>
> > Hi,
> >     Documentation for CKAN 2.2.
> > http://docs.ckan.org/en/ckan-2.2/user-guide.html#users-organizations-a
> > nd-authorization
> >
> > States "In the default setup, this dataset is initially private, and
> > visible only to other users in the same organization. When it is ready
> > for publication, it can be published at the press of a button. This
> > may require a higher authorization level within the organization."
> >
> > Suggesting there may be some differentiation in what roles can make a
> > dataset public.
> >
> > This documentation (for CKAN 2.3?) is more explicit
> > http://docs.ckan.org/en/latest/maintaining/authorization.html
> >
> > "An organization admin can:
> > ...
> > - Make datasets public or private.
> > ..."
> >
> > And this is the only role with that ability listed.
> >
> > In our install of CKAN 2.2 a user with role editor is able to create a
> > dataset and make it public or private, they can also switch datasets
> > that another user uploaded from private to public.  Is there a setting
> > that can limit the ability to make datasets public to only admin
> > users? And/or is this something that is coming in 2.3?
> >
> > Thanks
> > Aaron
> >
> > ________________________________
> >
>
>
> ________________________________
>
> Please consider the environment before printing this email
> Warning: This electronic message together with any attachments is confidential. If you receive it in error: (i) you must not read, use, disclose, copy or retain it; (ii) please contact the sender immediately by reply email and then delete the emails.
> The views expressed in this email may not be those of Landcare Research New Zealand Limited. http://www.landcareresearch.co.nz
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev

--
Nigel Babu
Developer, Open Knowledge