[ckan-dev] [ckan-discuss] VoID vocabulary integration

Thu May 24 14:01:01 UTC 2012

Thanks, Ross. I'll sniff around that.

Keith, feel free to hit me up off list if you'd like.

Regards,
-Tim

On May 24, 2012, at 9:54 AM, Ross Jones wrote:

> Hi,
> 
> I think I probably need to get some more input from the rest of the team on what 
> our preferred approach to doing this would be, although I wonder whether the simplest
> solution might be to try and build this into a CKAN extension rather than a separate 
> service. That would mean using Python and using the existing interfaces we have which
> are documented at http://docs.ckan.org/en/ckan-1.7/writing-extensions.html
> 
> I'll get some more feedback internally (and on list) but I suspect that would be the best way.
> 
> Ross
> 
> 
> On 24 May 2012, at 14:48, Timothy Lebo wrote:
> 
>> Similar to Keith, I could use some guidance for a transition path to incorporate this functionality.
>> 
>> Best,
>> Tim
>> 
>> On May 24, 2012, at 5:40 AM, Keith Alexander wrote:
>> 
>>> On Thu, May 24, 2012 at 10:01 AM, Ross Jones <ross.jones at okfn.org> wrote:
>>>> Hi,
>>>> 
>>>> On 24 May 2012, at 04:16, Keith Alexander wrote:
>>>>> (Though if people find it useful, it would be better hosted elsewhere
>>>>> long term. Could thedatahub.org host a service like this somehow,
>>>>> hopefully incorporating ideas from mine and Tim's code?)
>>>> 
>>>> With so many people implementing the same thing its probably wiser
>>>> that it be a part of thedatahub.  I'm keen to get features like this
>>>> implemented but the problem we have at present is finding the time
>>>> to do it. I wonder whether this is something that could be implemented
>>>> outside  of the core CKAN team, but as part of thedatahub so that it can
>>>> happen sooner rather than later?
>>>> 
>>>> Ross
>>> 
>>> What I did arose from a CKAN Skype telecon a whileback; I offered to
>>> create that void import service (somehow as part of the LATC work I
>>> was doing at Talis) with the vague idea that it could be hosted
>>> somewhere, and thedatahub front end  could make use of it somehow.
>>> 
>>> Do you have any ideas on the best way for thedatahub to incorporate
>>> this functionality (based on either mine, Tim's, or some new code)?
>>> And what requirements are there for this to happen? (language,
>>> framework, testing?)
>>> 
>>> I could imagine, for instance, a form, as part of the create and/or
>>> edit dataset page(s) that lets the user enter a dataset URI, and
>>> passes along the user's API key (with a hidden form field) and POSTs
>>> to my PHP service, which then redirects the user to the dataset page.
>>> 
>>> Cheers,
>>> 
>>> Keith
>>> 
>>>> 
>>>> _______________________________________________
>>>> ckan-dev mailing list
>>>> ckan-dev at lists.okfn.org
>>>> http://lists.okfn.org/mailman/listinfo/ckan-dev
>>> 
>>> _______________________________________________
>>> ckan-dev mailing list
>>> ckan-dev at lists.okfn.org
>>> http://lists.okfn.org/mailman/listinfo/ckan-dev
>>> 
>> 
>> 
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ckan-dev
> 
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev

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