2.0: Adding datasets to groups that you are not a part of

[frank0051]

Hi all, I think this might be a bug. Our install of 2.0 is from April 30 so this might have been fixed in one of the new contribs or there might be a config featuring were missing. In short:

The City of Houston and Code for Houston are trying to implement an open data portal for the region. The gameplan we’re discussing is for each government entity to be an organization with its own permissions while groups would be topical areas (like GIS, Environmental, Public Safety, etc.) and Departmental based catalogs of the datasets. Anyone in any of the organizations (or not in an organization who happens to have an account) could add their dataset to any one of the groups. In the CKAN demo site, any user can add a dataset to a group:
*See this dataset I added to the CKAN4RDM-test group: http://demo.ckan.org/dataset/test14

• You can also see I’m not a member of that group (there is only one member): http://demo.ckan.org/group/members/ckan4rdm-test

Over on our installation, however, I cannot add datasets to groups that weren't created by me (http://data.codeforhouston.com). We've tried adding logged_in as an editor and admin to some of the groups (feel free to try yourselves with group http://data.codeforhouston.com/group/members/city-of-houston-city-council), but that doesn't seem to be solving the problem. Is there some sort of commit that was added after April 30 or default setting in a config file that needs to be changed? If not, I think this might be a bug.

I know there is an outstanding issue to make it easier to find the permissions page for groups (#844) but that still doesn’t seem to solve the problem we're experiencing over on our side.

[frank0051]

I can confirm the Code of Houston site is performing the same way as the http://beta.ckan.org/ - so it looks like we're probably using same branch. I think part of the issue is already outlined in this issue (#843) where groups that you aren't a member of show up in the add groups dropdown and are able to be selected. That said, what's the difference between the Demo CKAN site (the one that allows you to add datasets to groups you are not a part of) and the Beta site? Could it be a commit caused this issue or could there be a setting that needs to be changed?

[newsroomdev]

Making @frank0051 an admin of the CKAN instance and asking for an admin list. You may close this issue.

[frank0051]

@geraldarthur, not quite sure that's the solution unless the http://demo.ckan.org automatically makes new users sysadmins. The question still remains: how is it that the demo site allows new users to add datasets to groups they aren't members of.

[newsroomdev]

@frank0051 cf the authorization documentation, what features are not currently in ckan2.0?

[frank0051]

@geraldarthur The issue we've run up against is users that are not admins or are not editors/admins of a group cannot add their datasets to a group. CKAN’s demo site (linked provided in the first post) allows new user accounts to add datasets to whatever group they want, whereas the beta site and our site does not. It isn't related to the anonymous users and best I can tell it isn't outlined on the authorization document.

See also #844 - adding members to groups is not very easy. But in either case, it does look like something (may it be configuration or may it be a commit) is different between the Demo CKAN site and the Beta CKAN site.

[tobes]

HI,

I think there are a couple of issues here.

a) Adding members to groups is difficult to do as although the functionality exists is was not in the templates. /group/members/<group_name> This will be fixed but in the 2.1 release

b) The adding removing datasets to/from groups needs some polish. There are some issues around this some are fix others may be outstanding. Again this should be improved in 2.1

[frank0051]

Hi @tobes , thanks for the response. While I definitely think those two issues are in the same wheelhouse (I even noticed the 1st open in the original post :-) ), I'm not sure either one is directly or indirectly responsible for what I'm getting at.

Please try this:

1. Create an account on http://demo.ckan.org
2. Add a new dataset. You'll notice your account is not part of an org, so you cannot add under an org.
3. Now add your new dataset to a group (any group) and you can. Even groups you are not part of you can add datasets to. You cannot do this on the beta Ckan site or our fresh install at Code for Houston.

Two examples:

1. Test dataset http://demo.ckan.org/dataset/test14 added to a group I'm not a member of : http://demo.ckan.org/group/members/ckan4rdm-test
2. Test dataset http://demo.ckan.org/dataset/test34 added to a different group I'm not a member of: http://demo.ckan.org/group/members/example-group

So, there is either something different between the commits, an extra mod on the demo side, or a config property we're all just completely missing. Any ideas?

[tobes]

Please try this:

1. Create an account on http://demo.ckan.org
2. Add a new dataset. You'll notice your account is not part of an org, so you cannot add under an org.
3. Now add your new dataset to a group (any group) and you can. Even groups you are not part of you can add > datasets to. You cannot do this on the beta Ckan site or our fresh install at Code for Houston.

This was a bug that has been fixed and should be in the 2.0 release - demo may not be running the latest 2.0 code. I can't find the issue as github search is now a real pain to use :(

[frank0051]

So @tobes, are we saying that this functionality of removing open groups (the ability to add datasets to groups you are not a part of) was planned? I'm just trying to get a sense of the direction we're moving in. If so, are there plans to reintroduce logged_in so we could mimic this functionality?

[tobes]

are we saying that this functionality of removing open groups (the ability to add datasets to groups you are not a part of) was planned? I'm just trying to get a sense of the direction we're moving in. If so, are there plans to reintroduce logged_in so we could mimic this functionality?

good question @shevski any thoughts?

Allowing 'open groups' should be easy enough for us to add probably via a config setting. logged_in is part of the old auth stuff that has been replaced. In 2.0 we really focused on the Organizations. I think in 2.1 we should be able to add some polish to the groups. We are aware of some issues like the adding members.

[newsroomdev]

@tobes they're on 2.1 so I could just replace bits of the new config with the old config? hm...

where can i find copies of prior versions of config files?

[tobes]

new code would need writing to enable this.

where can i find copies of prior versions of config files?

not sure what you mean with this but everything is in git.

[newsroomdev]

derp. kk, thanks

[amercader]

Closing as I think this has been fixed on recent CKAN versions, feel free to reopen if not