[ckan-dev] Data preview service

[Ross Jones]

Hi,

That's great news.  I'm a little unsure of the release cycle (3 months, 6
months?)  between point releases, so I guess it'd make sense for me to at
least extract it for the short term for those that are currently having
problems with it.  I'll also need a new backend for recline but I guess
yours is likely to be slightly different. Is there any
documentation,design,plans or wiki page for what you're building?

Ross.


On Wed, Feb 20, 2013 at 4:40 PM, Nigel Babu <nigel.babu at okfn.org> wrote:

> Hi Ross,
>
> Dominik and I have plans to do something about this.  Right now, we're a
> little occupied with other work, but the aim is to have something ready by
> CKAN 2.1 that would reduce the dependency on jsondataproxy.
>
>
> On 19 February 2013 21:27, Ross Jones <ross at servercode.co.uk> wrote:
>
>> Hi,
>>
>> I was speaking to some people at the CKAN 4 RDM workshop yesterday, and
>> one thing that came up as being broken right now, for some people, was data
>> preview via jsonpdataproxy.  Mostly this was because of their restrictive
>> internal firewall but it did mean that internally data preview didn't work
>> at all on CKAN.
>>
>> Is there a timeline for a localised re-write? If it is likely to be some
>> time away should I extract the data.gov.uk local data preview (which
>> works with archived, or remote resources) into a separate branch for those
>> people?
>>
>> Ross.
>>
>> _______________________________________________
>> 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
>>
>>
>
> _______________________________________________
> 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/20130220/718231c4/attachment-0001.html>