[ckan-dev] Next meetup: Drupal integration, 26 April

Thu Apr 12 19:22:39 UTC 2012

Paul,

I'm afraid Cabinet Office don't support this previously released
Drupal module. But it sounds like you're making headway.

You could see what response your local CKAN instance is giving to the
Drupal requests.

It probably isn't a CKAN version thing as the calls have been pretty
stable since the module release.

David

On 12 April 2012 20:12, Paul De Paula <paul at nuams.co> wrote:
> Hi,
>
> What will happen on april 26?. Im interested on the drupal discussion. I had
> a question on  the uk.gov.data released drupal module. I was able to
> sucessfully fetch data from datahub
> and converted it to nodes. Now my question is why it isnt working when i
> tried fetching the data from my own local ckan instance into my drupal
> instance? theyre both in the same server.
>
> Thanks,
>
> Paul
>
> -----------------------------------------------------------------------------------------
>>
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of ckan-dev digest..."
>>
>>
>> Today's Topics:
>>
>>   1. RFC snippets (Toby Dacre)
>>   2. Re: Misc feedback via Twitter (Toby Dacre)
>>   3. Re: Misc feedback via Twitter (Sean Hammond)
>>   4. solr wildcards (Toby Dacre)
>>   5. Re: Next meetup: Drupal integration, 26 April (David Read)
>>   6. Re: Misc feedback via Twitter (David Read)
>>   7. Use git submodules to manage recline in CKAN (Adri? Mercader)
>>   8. Re: Use git submodules to manage recline in CKAN
>>      (Friedrich Lindenberg)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Thu, 12 Apr 2012 12:05:19 +0100
>> From: Toby Dacre <toby.okfn at gmail.com>
>> Subject: [ckan-dev] RFC snippets
>> To: CKAN Development Discussions <ckan-dev at lists.okfn.org>
>> Message-ID:
>>
>>  <CAKZ3V-MXyC1sk_b1udj=hN5X=m-7_E-CCJR8qUvZMREaTEfn8A at mail.gmail.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> Hi,
>>
>> As work on cleaning our templates and aiding reuse/avoiding duplication
>> I've prototyped some snippet functionality.
>>
>> The idea is to have a folder of snippets in templates that can then be
>> rendered  as needed via a helper function.  This helps reduce the
>> size/complexity of _util.html etc.  It allows individual page components
>> to
>> be easily customised by extensions without duplicating content which
>> remains identical.
>>
>> example:
>>
>> ${h.snippet('package_list', packages=packages)}
>>
>> This renders the template "snippets/package_list.html" passing {'packages'
>> : packages} and inserts it into the page.
>>
>> Multiple keywords can be passed as needed which allows us to easily create
>> snippets from our existing xhtml
>> Any Genshi filters are applied to the rendered html
>>
>> Issues:
>> Should we be more explicit in passing the full template name?
>> Currently render() is partly reimplemented in snippet() - only about 10
>> lines of code for the whole function - is this a bad idea and all
>> rendering
>> should go through a single renderer?
>> Can anyone think of why snippets are a bad idea?
>> Any other thoughts?
>>
>> Toby
>>
>> PS I've also made a convert_to_dict() helper function so that we can
>> remove
>> further duplication in _util.html eg package_list() and
>> package_list_from_dict() which seems to work happily (at least for those
>> particular functions).
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> <http://lists.okfn.org/pipermail/ckan-dev/attachments/20120412/e21aa0bc/attachment-0001.htm>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Thu, 12 Apr 2012 12:20:46 +0100
>> From: Toby Dacre <toby.okfn at gmail.com>
>> Subject: Re: [ckan-dev] Misc feedback via Twitter
>> To: CKAN Development Discussions <ckan-dev at lists.okfn.org>
>> Message-ID:
>>
>>  <CAKZ3V-P0NmZuD-z8NmAdZOK6vu48=w40UBoUdSgH-ikFutDoSg at mail.gmail.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> On 12 April 2012 10:56, Mark Wainwright <mark.wainwright at okfn.org> wrote:
>>
>> > A couple of bits of feedback via twitter:
>> >
>> > Our own resting community co-ordinator Jonathan Gray would like to be
>> > able to sort search results - "(e.g. alphabetically, date of last
>> > edit, date added, etc)"
>> >
>> >
>> I think this is going to happen it is wanted for CMAP
>>
>>
>> > Edo Plantinga points out that the API links at the bottom of the page
>> > on the DataHub seem to be out of date. There's an odd link called API
>> > to <http://thedatahub.org/api/1>, and one called API Docs to a
>> > deprecated wiki page.
>> >
>> >
>> In master (dev release) API docs points to
>> http://docs.ckan.org/en/latest/api.html which looks correct to me
>>
>> the API link seems like it should be removed as it only shows the version
>> in json.  I think we should just remove this
>>
>> Toby
>>
>>
>> > Mark
>> >
>> >
>> > --
>> > Mark Wainwright, CKAN Community Co-ordinator
>> > Open Knowledge Foundation http://okfn.org/
>> > Skype: m.wainwright
>> >
>> > _______________________________________________
>> > 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/20120412/37614cc9/attachment-0001.htm>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Thu, 12 Apr 2012 13:23:29 +0200
>> From: Sean Hammond <sean.hammond at okfn.org>
>> Subject: Re: [ckan-dev] Misc feedback via Twitter
>> To: ckan-dev at lists.okfn.org
>> Message-ID: <20120412112329.GL367 at sooty.fritz.box>
>> Content-Type: text/plain; charset=us-ascii
>>
>> > > Edo Plantinga points out that the API links at the bottom of the page
>> > > on the DataHub seem to be out of date. There's an odd link called API
>> > > to <http://thedatahub.org/api/1>, and one called API Docs to a
>> > > deprecated wiki page.
>> > >
>> > >
>> > In master (dev release) API docs points to
>> > http://docs.ckan.org/en/latest/api.html which looks correct to me
>>
>> Yes I fixed that link in master last week.
>>
>>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Thu, 12 Apr 2012 17:35:19 +0100
>> From: Toby Dacre <toby.okfn at gmail.com>
>> Subject: [ckan-dev] solr wildcards
>> To: CKAN Development Discussions <ckan-dev at lists.okfn.org>
>> Message-ID:
>>
>>  <CAKZ3V-O1+n12iJTyirgohpTeos08VmpcF8qhOU42GHOGhVLDfw at mail.gmail.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> Adria/David Raz,
>>
>> as well as
>>
>> <dynamicField name="*" type="string" indexed="true"  stored="false"/>
>>
>> is it also worth adding some other wildcards to reduce the number of
>> schema
>> changes?
>>
>> <dynamicField name="*_int" type="int" indexed="true"  stored="false"/>
>> <dynamicField name="*_datetime" type="datetime" indexed="true"
>> stored="false"/>
>>
>> Toby
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> <http://lists.okfn.org/pipermail/ckan-dev/attachments/20120412/eec26eea/attachment-0001.htm>
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Thu, 12 Apr 2012 18:19:43 +0100
>> From: David Read <david.read at hackneyworkshop.com>
>> Subject: Re: [ckan-dev] Next meetup: Drupal integration, 26 April
>> To: CKAN Development Discussions <ckan-dev at lists.okfn.org>
>> Cc: CKAN discuss <ckan-discuss at lists.okfn.org>
>> Message-ID:
>>
>>  <CAOY41VUAH5TL2PNLpnCNBEbmD9e8dyJoCsBybWHKpHvSjyJxuQ at mail.gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>>
>> It would be great if a technical OKF person was involved in this
>> discussion too - I'm very keen to hear about the Drupal 7 work they
>> are currently involved with.
>>
>> David
>>
>> On 11 April 2012 11:43, Mark Wainwright <mark.wainwright at okfn.org> wrote:
>> > The next CKAN online meetup will be on Drupal integration, on Thursday
>> > 26 April at 5pm UK time. Anyone who is interested is welcome to
>> > attend.
>> >
>> > Drupal is a powerful and very widely-used content management system.
>> > It's already integrated with CKAN's data management system in some
>> > deployments, notably at data.gov.uk. What needs to be done to make
>> > this easier to replicate? What features would help?
>> >
>> > To attend the meeting, sign up with your skype id on the etherpad here
>> > - please also add any specific topic areas you'd like to discuss:
>> >
>> > http://ckan.okfnpad.org/meetup-2012-04-26
>> >
>> > Mark
>> >
>> >
>> > --
>> > Mark Wainwright, CKAN?Community Co-ordinator
>> > Open Knowledge Foundation?http://okfn.org/
>>
>> > Skype: m.wainwright
>> >
>> > _______________________________________________
>> > ckan-dev mailing list
>> > ckan-dev at lists.okfn.org
>> > http://lists.okfn.org/mailman/listinfo/ckan-dev
>>
>>
>>
>> ------------------------------
>>
>> Message: 6
>> Date: Thu, 12 Apr 2012 18:32:27 +0100
>> From: David Read <david.read at hackneyworkshop.com>
>> Subject: Re: [ckan-dev] Misc feedback via Twitter
>> To: CKAN Development Discussions <ckan-dev at lists.okfn.org>
>> Message-ID:
>>
>>  <CAOY41VUBXfAeEj4mGP752yc9OG-RWhsT8MQ9tr7UNNj8-xzm9w at mail.gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> On 12 April 2012 12:20, Toby Dacre <toby.okfn at gmail.com> wrote:
>> >
>> >
>> > On 12 April 2012 10:56, Mark Wainwright <mark.wainwright at okfn.org>
>> > wrote:
>> >>
>> >> A couple of bits of feedback via twitter:
>> >>
>> >> Our own resting community co-ordinator Jonathan Gray would like to be
>> >> able to sort search results - "(e.g. alphabetically, date of last
>> >> edit, date added, etc)"
>>
>> We had that put in at data.gov.uk recently. Ian has the patch.
>>
>> David
>>
>> >>
>> >
>> > I think this is going to happen it is wanted for CMAP
>> >
>> >>
>> >> Edo Plantinga points out that the API links at the bottom of the page
>> >> on the DataHub seem to be out of date. There's an odd link called API
>> >> to <http://thedatahub.org/api/1>, and one called API Docs to a
>> >> deprecated wiki page.
>> >>
>> >
>> > In master (dev release) API docs points to
>> > http://docs.ckan.org/en/latest/api.html which looks correct to me
>> >
>> > the API link seems like it should be removed as it only shows the
>> > version in
>> > json.? I think we should just remove this
>> >
>> > Toby
>> >>
>> >> Mark
>> >>
>> >>
>> >> --
>> >> Mark Wainwright, CKAN?Community Co-ordinator
>> >> Open Knowledge Foundation?http://okfn.org/
>>
>> >> Skype: m.wainwright
>> >>
>> >> _______________________________________________
>> >> 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
>> >
>>
>>
>>
>> ------------------------------
>>
>> Message: 7
>> Date: Thu, 12 Apr 2012 19:44:25 +0100
>> From: Adri? Mercader <amercadero at gmail.com>
>> Subject: [ckan-dev] Use git submodules to manage recline in CKAN
>> To: CKAN Development Discussions <ckan-dev at lists.okfn.org>
>> Message-ID:
>>
>>  <CA+Tg0CbAqv8ye2GhwyOG+=0miABPyQfRiDkVPzqerCdjm9KXMg at mail.gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> Hi all,
>>
>> I don't have many experience with them, but Rufus mentioned that it
>> may be worth using git submodules to manage external repos in CKAN
>> source, like recline.
>>
>> I had a quick look and they look quite useful, and I think we are
>> already using them for some docs theme repo. Has anyone any
>> experience, reservations, thoughts about them?
>> Will they affect the deployment, packaging process?
>>
>> Adri?
>>
>>
>>
>> ------------------------------
>>
>> Message: 8
>> Date: Thu, 12 Apr 2012 20:50:36 +0200
>> From: Friedrich Lindenberg <friedrich.lindenberg at okfn.org>
>> Subject: Re: [ckan-dev] Use git submodules to manage recline in CKAN
>> To: CKAN Development Discussions <ckan-dev at lists.okfn.org>
>> Message-ID: <9FC85A689CEB42DEB0FE1512CDF81FB4 at okfn.org>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hey,
>>
>> we're using them in OpenSpending and they are clearly the right solution
>> in theory. In practice, keeping them in sync, making sure they get deployed
>> when necessary and explaining them to people who just want to play with your
>> codebase has proven a horrible PITA.
>>
>> I think we're now moving to a model where the URL of that sub-component is
>> configurable (openspendingjs, as openspending.script_root in the .ini) so
>> people can either check it out into pylons' public/ directory or just set
>> another path (I have apache running locally and share my code root on
>> localhost). The nice side-effect of this is that it forces you to use url
>> builder helpers for assets, so you get asset subdomains, cache-bombing etc.
>> for free.
>>
>> - Friedrich
>>
>>
>> On Thursday, April 12, 2012 at 8:44 PM, Adri? Mercader wrote:
>>
>> > Hi all,
>> >
>> > I don't have many experience with them, but Rufus mentioned that it
>> > may be worth using git submodules to manage external repos in CKAN
>> > source, like recline.
>> >
>> > I had a quick look and they look quite useful, and I think we are
>> > already using them for some docs theme repo. Has anyone any
>> > experience, reservations, thoughts about them?
>> > Will they affect the deployment, packaging process?
>> >
>> > Adri?
>> >
>> > _______________________________________________
>> > ckan-dev mailing list
>> > ckan-dev at lists.okfn.org (mailto: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/20120412/314dcfc2/attachment.htm>
>>
>> ------------------------------
>>
>>
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ckan-dev
>>
>>
>> End of ckan-dev Digest, Vol 18, Issue 11
>> ****************************************
>
>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>