[ckan-dev] API call organization_update clears the user list for organization

[Ian Ward]

ckanapi's "load organizations" command has a workaround for this this
issue[1]. I agree, we should change the API to accept a missing users
key to mean "don't change" the same way a missing resources key means
"don't change" in package_update. At the same time we should document
all the special/possibly unexpected behaviours for each common key in
the *_update functions.

[1]: https://github.com/ckan/ckanapi/blob/master/ckanapi/cli/load.py#L215-L229

On Fri, Oct 3, 2014 at 9:00 AM, David Read
<david.read at hackneyworkshop.com> wrote:
> Milica,
>
> Yes there are others including me that want this. There are various
> ways it could be done - an option to say "don't change the users", or
> just leave them alone if you don't specify the 'users' key - as
> proposed here:
> https://github.com/ckan/ckan/issues/1907
>
> David
>
> On 30 September 2014 10:57, Milica Knezevic <knezevic.milica at gmail.com> wrote:
>> Hi,
>>
>> In CKAN 2.2 API call organization_update clears the user list for
>> organization if user list is not specified. Is there a way (setting
>> additional parameter or smth similar) that would enable user list
>> (membership) to be preserved if not specified in the call?
>>
>> Thanks,
>> Milica
>>
>> _______________________________________________
>> 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
>>
> _______________________________________________
> 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