CKAN: Ticket #816: Autocomplete for the resource format field

milestone changed; priority, repo, state, theme set

dread — Mon, 16 May 2011 15:26:20 GMT

priority set to awaiting triage
repo set to ckan
state set to draft
theme set to none
milestone changed from ckan-v1.4 to ckan-v1.5

status changed; owner set

thejimmyg — Wed, 20 Jul 2011 14:17:46 GMT

owner set to johnglover
status changed from new to assigned

John, could you have a look at this one please. We'd need an entry in the logic layer for it and then some autocomplete JavaScript? on the format field.

Can we standardise on jQueryUI going forward.

http://jqueryui.com/demos/autocomplete/

priority, type, milestone changed

thejimmyg — Wed, 20 Jul 2011 14:43:41 GMT

priority changed from awaiting triage to minor
type changed from requirement to enhancement
milestone changed from ckan-v1.5 to ckan-current-sprint

rgrp — Mon, 01 Aug 2011 09:54:59 GMT

What about idea of 'model' refactor for resource, specifically to have:

format: human created format string with possible nesting e.g. zip:csv
kind: file | api | example | service
mimetype: standard mimetype (e.g. for zipped csv would be application/zip)
mimetype-inner: mimetype of innermost object (so for example would be text/csv)

See http://lists.okfn.org/pipermail/ckan-discuss/2011-April/001139.html

dread — Mon, 01 Aug 2011 15:33:02 GMT

I like rgrp's idea to change the model. But since it's complicated it would be good to have a UI.

e.g. You might make format field simply a drop-down with only some common options: 'CSV, Excel, Zip, Other'. If you go for Other, then a more substantial UI appears, to cover more filetypes, APIs, services and a text box for Other. And if you select 'Zip' then another set of options appears to say what is in the zip. etc.etc.

Another approach would be to have a background process downloading the data file and filling this in for you.

status changed; resolution set

johnglover — Tue, 02 Aug 2011 14:29:31 GMT

status changed from assigned to closed
resolution set to fixed

I have implemented the resource autocomplete so am closing this for now.

I agree that more information on the resource would be a good addition. It seems a bit of a different issue to just adding autocomplete though, with potentially far more changes to the codebase, so maybe it would be better discussed in a separate ticket/CREP. However, any new fields would presumably want to either be constrained or have an autocomplete and so can reuse the work done on this feature.

Cheers, John

dread — Fri, 28 Oct 2011 12:24:58 GMT

John did this in cset:1697dfa2552c for release 1.5

dread — Fri, 28 Oct 2011 14:32:04 GMT

And branch feature-816-format-autocomplete