[ckan-dev] Urgent: org changes clarification

Thu Sep 27 15:32:27 UTC 2012

On Thu, Sep 27, 2012 at 12:55:28PM +0100, Toby Dacre wrote:
> On 27 September 2012 12:40, Sean Hammond <sean.hammond at okfn.org> wrote:
> >> from
> >>
> >> https://raw.github.com/okfn/ckan/c49c3d7a6e6a635ceecd796b55a679f519242830/doc/organizations_and_groups.rst
> >>
> >>
> >> * **Anyone** can see a list of all an organization's _public_ datasets
> >> * **Anyone** can see a list of all a group's datasets (groups can't
> >> have private datasets, they're all public)
> >>
> >> This is contradictory/broken logic
> >>
> >> options
> >>
> >> a) any dataset can be in a group but viewers of the group only see
> >> datasets they can see
> >> b) any private datasets are never seen as groups datasets even though
> >> they may be in the group
> >> c) if a dataset becomes private it is removed from ALL groups it is in
> >> (REGARDLESS of any rights they have to ANY of those groups)
> >>
> >>
> >> I vote for (b) what do people think?
> >
> > I see what you mean. (a) is simpler than (b), because if a dataset
> > belongs to some groups and then it gets made private it simply still
> > belongs to those groups, but people won't see it unless they're a member
> > of its organization. Then if it gets made public again, it just
> > continues belonging to the same groups but people can see it now. Would
> > be the same for tags, from the user's point of view.
> >
> 
> I disagree
> 
> b) is easy as all users see the same results for the group so group
> list stays simple just filters out private datasets
> 
> a) is essentially the same as b except we need to now worry about the
> users orgs etc so add that complication to group list
> 
> for b) the dataset stays in the group but is hidden

Alright, that sounds simplest, lets do it that way.

> > Anyway, I think the plan is to implement organizations as described in
> > the spec but to leave groups as they are currently (and not try to make
> > them match the spec) and to remove groups from the frontend and replace
> > them with organizations. So CKAN 2.0 will have only organizations and
> > not groups, although in the backend the groups feature would still be
> > there and could be finished off at some point. That's what we agreed
> > right?
> >
> yeah but they need to change as regards private datasets

Alright, I think I got confused about this and actually we do want both
groups and orgs in the frontend for 2.0.