Changes between Version 4 and Version 5 of Ticket #1744


Ignore:
Timestamp:
02/10/12 12:54:39 (2 years ago)
Author:
zephod
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1744 – Description

    v4 v5  
    55    * 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' 
    66  * Show edit summary form again, at least on edit pages (and prefill it for create to something sensible like: Creating dataset {title} {name}) 
    7   * Fix drop down for resource types in resource add/edit to limit to fixed set of options (as per http://wiki.ckan.org/Domain_Model/Resource) 
    8     * See also http://lists.okfn.org/pipermail/ckan-discuss/2011-December/001860.html 
     7  * ~~Fix drop down for resource types in resource add/edit to limit to fixed set of options (as per http://wiki.ckan.org/Domain_Model/Resource)~~ 
     8    * ~~See also http://lists.okfn.org/pipermail/ckan-discuss/2011-December/001860.html~~ 
    99  * 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)) 
    1010    * 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)