[ckan-dev] organization deletion

Mon Oct 8 12:33:14 UTC 2012

Hello,

The logic was that, on most instances, because org admins are not
allowed to make an organization they should not be able to delete them
either.  These are the relevant user stories:

* **Users** can create new organizations, if this is enabled in the config
  file (boolean option), and will automatically become admin of the new
  organization
* **Users** can create new groups, if this is enabled in the config
  file (another boolean option), and will automatically become admin of the new
  group

I think these boolean options should define if an admin of the
group/org can delete the group/org as well. i.e if a user is allowed
to make a group/org then they are allowed to delete it too.

The case of ec is they have a predefined list of orgs and deleting them
by the org admins (by mistake or otherwise) would cause pain.

Thanks

David

On Wed, Oct 3, 2012 at 2:54 PM, Toby Dacre <toby.okfn at gmail.com> wrote:
> On 3 October 2012 14:49, Sean Hammond <sean.hammond at okfn.org> wrote:
>>> According to
>>>
>>> https://raw.github.com/okfn/ckan/c49c3d7a6e6a635ceecd796b55a679f519242830/doc/organizations_and_groups.rst
>>>
>>> an group admin can delete a group but an org admin cannot delete an
>>> org is there a logic to this it just seems to add complexity for no
>>> benefit.  Is there a valid reason
>>
>> Afaik this wasn't a deliberate decision looks like an accidental
>> omission, I would say org admin or sysadmin can delete org, perhaps
>> kindly would disagree
>>
> This would mean that the permissions for both groups and orgs remain
> in sync even if some of the 'logic' and 'auth' functions differ
> also this is now implemented
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ckan-dev
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev