http://localhost/ticket/978 <p> Following on from <a class="closed ticket" href="http://localhost/ticket/826" title="enhancement: Resource 'extra' fields (closed: fixed)">#826</a> - we can configure some extra fields in resources and can edit them in the Web UI, but we can't create new columns in the Web UI. This ticket is to allow this. </p> <p> Implementation ============== I envisage a 'add column' button that allows you to add this a property to all resources in a package. I'd rather not have a sub-form as that could be logistically difficult. You could either make the 'extra' column titles editable or provide a button to edit them. </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/978 Trac 0.12.3 dread Fri, 11 Feb 2011 13:19:30 GMT http://localhost/ticket/978#comment:1 http://localhost/ticket/978#comment:1 <ul> <li><strong>description</strong> modified (<a href="/ticket/978?action=diff&amp;version=1">diff</a>) </li> </ul> Ticket rgrp Sat, 27 Aug 2011 00:27:38 GMT http://localhost/ticket/978#comment:2 http://localhost/ticket/978#comment:2 <ul> <li><strong>repo</strong> set to <em>ckan</em> </li> <li><strong>theme</strong> set to <em>none</em> </li> </ul> <p> Suggest we either a) get rid of columnar layout or b) (preferable) get a dedicated page for resource. That way summary on package page just shows main attributes. </p> Ticket rgrp Fri, 30 Dec 2011 15:34:26 GMT http://localhost/ticket/978#comment:3 http://localhost/ticket/978#comment:3 <ul> <li><strong>summary</strong> changed from <em>Web UI for Resource Extras</em> to <em>Edit Resource Extras in Web UI</em> </li> </ul> <p> Think this should be part of a larger refactor of resource editing now that <a class="closed ticket" href="http://localhost/ticket/1445" title="enhancement: Resource View page in WUI (closed: fixed)">#1445</a> (resource page in WUI) is done </p> Ticket rgrp Mon, 06 Feb 2012 12:12:18 GMT http://localhost/ticket/978#comment:4 http://localhost/ticket/978#comment:4 <ul> <li><strong>owner</strong> set to <em>zephod</em> </li> <li><strong>status</strong> changed from <em>new</em> to <em>assigned</em> </li> <li><strong>milestone</strong> changed from <em>ckan-backlog</em> to <em>current-ckan-sprint-2012-02-20</em> </li> </ul> Ticket rgrp Mon, 06 Feb 2012 12:13:45 GMT http://localhost/ticket/978#comment:5 http://localhost/ticket/978#comment:5 <ul> <li><strong>summary</strong> changed from <em>Edit Resource Extras in Web UI</em> to <em>Edit Resource including Extras in Web UI</em> </li> </ul> Ticket rgrp Mon, 06 Feb 2012 12:14:19 GMT http://localhost/ticket/978#comment:6 http://localhost/ticket/978#comment:6 <p> We already have basic editing in the Resource section of dataset edit. However, need to extend this to additional fields such as webstore_url and "extras". </p> Ticket rgrp Fri, 10 Feb 2012 12:15:17 GMT http://localhost/ticket/978#comment:7 http://localhost/ticket/978#comment:7 <ul> <li><strong>description</strong> modified (<a href="/ticket/978?action=diff&amp;version=7">diff</a>) </li> </ul> Ticket zephod Mon, 27 Feb 2012 13:17:59 GMT http://localhost/ticket/978#comment:8 http://localhost/ticket/978#comment:8 <ul> <li><strong>description</strong> modified (<a href="/ticket/978?action=diff&amp;version=8">diff</a>) </li> </ul> Ticket zephod Mon, 27 Feb 2012 13:19:40 GMT http://localhost/ticket/978#comment:9 http://localhost/ticket/978#comment:9 <ul> <li><strong>description</strong> modified (<a href="/ticket/978?action=diff&amp;version=9">diff</a>) </li> </ul> Ticket zephod Wed, 29 Feb 2012 20:23:32 GMT http://localhost/ticket/978#comment:10 http://localhost/ticket/978#comment:10 <ul> <li><strong>description</strong> modified (<a href="/ticket/978?action=diff&amp;version=10">diff</a>) </li> </ul> Ticket zephod Wed, 29 Feb 2012 20:26:21 GMT http://localhost/ticket/978#comment:11 http://localhost/ticket/978#comment:11 <ul> <li><strong>status</strong> changed from <em>assigned</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>fixed</em> </li> </ul> <p> This was not trivial to implement. The backend supports arbitrary key/value pairings on resources, and the frontend can now handle this. Add, edit and delete resource extras according to the form state. </p> <p> I had to make a modification to the backend: When saving a resource, you have to submit the complete set of extras. Unsubmitted extras are assumed to be deleted. (This matches the behaviour of the package form). </p> <p> <a class="ext-link" href="https://github.com/okfn/ckan/commit/a41cd0c9b04c757f5fa37acaba6be71e345a9c1f#L0R39"><span class="icon">​</span>https://github.com/okfn/ckan/commit/a41cd0c9b04c757f5fa37acaba6be71e345a9c1f#L0R39</a> </p> Ticket