[ckan-dev] Harvesting of organizations

Dave Caraway dave at fogmine.com
Wed Aug 14 22:18:33 UTC 2013


i'm really interested in this capability. i would say with regard to
creating organizations automatically, might want to make it optional. the
underlying question, should a typo in a name cause a new org to be created?



On Aug 14, 2013, at 11:51 AM, Stefan Oderbolz <stefan.oderbolz at liip.ch>
wrote:

Hi there,

I'm planning to implement the harvesting of organizations in the
ckanext-harvest extension. As the harvesting of groups (using the
remote_groups config option) is already implemented, I guess this shouldn't
be that hard.

In the current code all I found was this:

# Ignore remote orgs for the time being
package_dict.pop('owner_org', None)

Are there already thoughts about this topic? Currently I'm planning to just
create the organizations that are not yet there and assign all datasets to
their corresponding owner organization (very similar to the implementation
of the remote_groups). The purpose is not to copy users/permissions etc.
but to simply allow all data owners to see their datasets at a glance on
the central instance and provide the functionality to filter datasets of an
organization.

What do you think?

Regards Stefan

-- 
Liip AG  //  Feldstrasse 133 //  CH-8004 Zurich
Tel +41 43 500 39 80 // GnuPG 0x7B588C67 // www.liip.ch

_______________________________________________
ckan-dev mailing list
ckan-dev at lists.okfn.org
http://lists.okfn.org/mailman/listinfo/ckan-dev
Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20130814/0355047b/attachment-0001.html>


More information about the ckan-dev mailing list