http://localhost/ticket/1744 <p> Super ticket: <a class="closed ticket" href="http://localhost/ticket/1506" title="enhancement: [super] UX improvements to dataset edit, create and search + group + user ... (closed: fixed)">#1506</a> </p> <ul><li>Fix (i.e. allow / show) name editing on dataset edit. <ul><li>Fix the slugify so it does not overwrite if i change title after fixing name. </li><li>Make slugify encourage people to use shorter names. Either by cutting off (not so good) or showing a warning and saying something like 'hey you may want to cut this down. Hit edit to customize the dataset name now' </li></ul></li><li>Show edit summary form again, at least on edit pages (and prefill it for create to something sensible like: Creating dataset {title} {name}) </li><li>Fix drop down for resource types in resource add/edit to limit to fixed set of options (as per <a class="ext-link" href="http://wiki.ckan.org/Domain_Model/Resource"><span class="icon">​</span>http://wiki.ckan.org/Domain_Model/Resource</a>) <ul><li>See also <a class="ext-link" href="http://lists.okfn.org/pipermail/ckan-discuss/2011-December/001860.html"><span class="icon">​</span>http://lists.okfn.org/pipermail/ckan-discuss/2011-December/001860.html</a> </li></ul></li><li>Allow reordering of resources (or: and this is somewhat more complex but possibly simpler: allow editing of a resource_order field and we use that to sort resources (this is more like wordpress page_order -- these two options could become the same if we just hijack the existing position field on the join table and get rid of ordereredlist extension)) <ul><li>Alternative/complement: forget ordering of resources and just allow for simple search on dataset page (do it in pure js). Would still need a default ordering (with editing of extra fields could allow users to add a position field to each resource) </li></ul></li><li>Merge Groups and Tags into main Edit section (no point having them on their own and most people will miss this). </li><li>Radically simplify set of licenses - <a class="closed ticket" href="http://localhost/ticket/1359" title="enhancement: Radically simplify standard list of licenses (closed: fixed)">#1359</a> [ assigned to rgrp ] </li><li>Clarify that additional info = extra fields + add guidance - <a class="closed ticket" href="http://localhost/ticket/1648" title="enhancement: Clarify that additional info = extra fields + add guidance (closed: fixed)">#1648</a> (minor? wontfix?) </li><li><del>"Unsaved changes" warning briefly when you click "Save" <a class="closed ticket" href="http://localhost/ticket/1735" title="enhancement: &#34;Unsaved changes&#34; warning briefly when you click &#34;Save&#34; (closed: wontfix)">#1735</a></del> </li><li><del>"Unsaved changed" typo on dataset edit page</del> </li><li><del>Force format field to be lower case (with a little bit of javascript!)</del> <ul><li>Why? I think pages like this look nicely formatted: <a class="ext-link" href="http://thedatahub.org/dataset/1996_population_census_data_canada"><span class="icon">​</span>http://thedatahub.org/dataset/1996_population_census_data_canada</a> </li><li>Shouldn't this be enforced in the commit/validate step of the logic layer rather than JS in the front-end? </li></ul></li></ul> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/1744 Trac 0.12.3 rgrp Mon, 06 Feb 2012 11:05:58 GMT http://localhost/ticket/1744#comment:1 http://localhost/ticket/1744#comment:1 <ul> <li><strong>milestone</strong> changed from <em>ckan-v1.6</em> to <em>ckan-sprint-2012-02-20</em> </li> </ul> Ticket zephod Mon, 06 Feb 2012 12:22:57 GMT http://localhost/ticket/1744#comment:2 http://localhost/ticket/1744#comment:2 <ul> <li><strong>description</strong> modified (<a href="/ticket/1744?action=diff&amp;version=2">diff</a>) </li> </ul> Ticket rgrp Tue, 07 Feb 2012 10:14:50 GMT http://localhost/ticket/1744#comment:3 http://localhost/ticket/1744#comment:3 <ul> <li><strong>description</strong> modified (<a href="/ticket/1744?action=diff&amp;version=3">diff</a>) </li> </ul> Ticket zephod Fri, 10 Feb 2012 12:53:41 GMT http://localhost/ticket/1744#comment:4 http://localhost/ticket/1744#comment:4 <ul> <li><strong>description</strong> modified (<a href="/ticket/1744?action=diff&amp;version=4">diff</a>) </li> </ul> Ticket zephod Fri, 10 Feb 2012 12:54:39 GMT http://localhost/ticket/1744#comment:5 http://localhost/ticket/1744#comment:5 <ul> <li><strong>description</strong> modified (<a href="/ticket/1744?action=diff&amp;version=5">diff</a>) </li> </ul> Ticket zephod Mon, 27 Feb 2012 13:21:17 GMT http://localhost/ticket/1744#comment:6 http://localhost/ticket/1744#comment:6 <ul> <li><strong>description</strong> modified (<a href="/ticket/1744?action=diff&amp;version=6">diff</a>) </li> </ul> Ticket zephod Mon, 27 Feb 2012 13:31:12 GMT http://localhost/ticket/1744#comment:7 http://localhost/ticket/1744#comment:7 <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>fixed</em> </li> <li><strong>description</strong> modified (<a href="/ticket/1744?action=diff&amp;version=7">diff</a>) </li> </ul> <p> Massive refactor of parent ticket mean this is all done and can be closed off. See <a class="closed ticket" href="http://localhost/ticket/1506" title="enhancement: [super] UX improvements to dataset edit, create and search + group + user ... (closed: fixed)">#1506</a> for remaining UX work. </p> Ticket