Jonathan Gray

Dr. Jonathan Gray is author of Public Data Cultures and Reader in Critical Infrastructure Studies at the Department of Digital Humanities, King’s College London. He is also Cofounder of the Public Data Lab; and Research Associate at the Digital Methods Initiative (University of Amsterdam) and the médialab (Sciences Po, Paris). More about his work can be found at jonathangray.org.

More Reading

Post navigation

3 Comments

  • Hi, sounds like an interesting meeting – not sure if I’ll be able to make it though.

    Maybe I can drop in a couple of my CKAN wishlist items here:

    • when adding a package it would be great to specify a group the package belongs to on the package page (preferably via an autocomplete field)
    • adding autocomplete to the tags field would help reduce the number of similar tags
    • I’d love to see some delete functions added to the API – even if only available in dev mode – it’s hard to write repeatable tests against CKAN when you can’t clean up the test results
    • It would be helpful to have the option to receive the notes data as processed html rather than raw markdown, this would also make it possible to have ckan instances with WYSIWYG notes fields saving html to the database (I realise though that this would be an API change).
    • wildcard searches would be very useful (and search results on partial matches)
    • API – package creation date and package update date in results
    • API – interface to history
    • API – interface to most recent packages – and even better those since $date
    • Validation – ensure URLS are valid (or at least reasonable
    • Extras – allow sitewide definitions – so a CKAN instance can define all packages to have a ‘foo’ field that doesn’t have to be created for each package (ideally these could also have validation rules)

    Well I hope that’s helpful – sorry if it’s a bit of a long list.

    Sean

Leave a Reply

Your email address will not be published. Required fields are marked *

back to top