[ckan-dev] Publisher profile

[Ross Jones]

Ah okay, no, you’re not missing out on anything with the publisher profile :)

To only let the creator (see https://github.com/ckan/ckan/blob/master/ckan/model/package.py#L47 which I think is reasonably new) and admin view private packages, I suspect overriding package_show auth function in a plugin (that implements IAuthFunctions) should give you what you’re after. If you already have a plugin then you can have it implement IAuthFunctions directly.

The current implementation is at https://github.com/ckan/ckan/blob/master/ckan/logic/auth/get.py#L97  and I think you’ll probably want to have some more logic around about https://github.com/ckan/ckan/blob/master/ckan/logic/auth/get.py#L110

Ross.

On 5 Feb 2014, at 16:36, Pabitra Dash <pkdash_reena at hotmail.com> wrote:

> No. I am not using publisher profile. I just came across  this feature somewhere in the document and got curious to find out more about it thinking it might be something additional access control that one can do using the publisher profile. I am using organization for dataset access control. 
>  
> I am facing a challenge though as it relates publishing workflow. We want all dataset when first created to be private (which we can do). We want only the admin of the organization and the owner/creator of these private datasets to have access to these datasets until they are made public by the admin of the organization (this is what we have not been able to implement yet). At this point all the members of an organization are able to see all the private datasets (default CKAN behavior). 
>  
> Any idea how we can solve our publishing workflow needs?
>  
> Thanks,
>  
> Pabitra
> Utah State University
> Logan UT USA
> 
> 
>  
> From: ross at servercode.co.uk
> Date: Wed, 5 Feb 2014 16:05:24 +0000
> To: ckan-dev at lists.okfn.org
> Subject: Re: [ckan-dev] Publisher profile
> 
> Hi,
> 
> Publisher profiles don’t provide anything that isn’t available in Organisations.  If you’re still using the publisher profile it would make sense to migrate over to using organisations sooner rather than later, because at some point it’ll stop working.  As far as I am aware it was only really intended for the 1.x branch whilst organisations were implemented in the 2.x branch to provide the same (and more) functionality.
> 
> Perhaps I am misunderstanding though, what are you trying to achieve, is it possible to give an example?
> 
> Ross.
> 
> 
> On 5 Feb 2014, at 16:02, Pabitra Dash <pkdash_reena at hotmail.com> wrote:
> 
> Hi Ross,
>  
> I was thinking the publisher profile is an additional feature on top of  access/workflow control one can achieve through organization. I am running version 2.1 and soon will be updating to 2.2.
>  
> Thanks for your response.
>  
> Pabitra
> 
> Utah State University,
> Logan, UT, USA
>  
> From: ross at servercode.co.uk
> Date: Wed, 5 Feb 2014 08:49:01 +0000
> To: ckan-dev at lists.okfn.org
> Subject: Re: [ckan-dev] Publisher profile
> 
> Hi,
> 
> Publisher functionality is now provided by organizations in CKAN which is described at http://docs.ckan.org/en/latest/user-guide.html#users-organizations-and-authorization, are you upgrading from 1.x and need to migrate data?
> 
> Ross 
> 
> On 5 Feb 2014, at 06:23, Pabitra Dash <pkdash_reena at hotmail.com> wrote:
> 
> Hi All,
>  
> I was wondering if this feature (publisher profile) is still available in version2.1/2.2
>  
> http://docs.ckan.org/en/master/publisher-profile.html
>  
> Thanks,
> Pabitra
> 
> 
> _______________________________________________
> 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.orghttps://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
> 
> 
> _______________________________________________ ckan-dev mailing list ckan-dev at lists.okfn.orghttps://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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20140205/1a123226/attachment-0003.html>