[ckan-dev] Private resources and public datasets

Guillaume Sueur no-reply at neogeo-online.net
Fri Apr 7 09:52:33 UTC 2017


whaouh, that looks good ! THanks !

Le 07/04/2017 à 11:19, Harald von Waldow a écrit :
> You might want to have a look at Lucia's ckanext-restricted:
> https://github.com/espona/ckanext-restricted
> 
> Cheers,
> Harald
> 
> On 2017-04-07 10:36, Guillaume Sueur wrote:
>> Hi list,
>>
>> Even if I've noticed this not so long ago thread
>> (https://lists.okfn.org/pipermail/ckan-dev/2016-August/010168.html) I
>> just wanted to ask the core developers and maintainers of CKAN the same
>> question :
>> Is there by any chance a way to manage different rights on resources and
>> datasets, allowing a public exposed dataset to contain both public and
>> privates resources ?
>> If not, is this approach completely out of current scope / architecture
>> / design or is it something that could be considered with an appropriate
>> funding ?
>>
>> Best regards
>>
>> Guillaume
>> _______________________________________________
>> 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
> 



More information about the ckan-dev mailing list