Changes between Version 6 and Version 7 of Ticket #1744


Ignore:
Timestamp:
02/27/12 13:31:12 (2 years ago)
Author:
zephod
Comment:

Massive refactor of parent ticket mean this is all done and can be closed off. See #1506 for remaining UX work.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1744

    • Property Status changed from new to closed
    • Property Resolution changed from to fixed

  • Ticket #1744 – Description

    v6 v7  
    11Super ticket: #1506 
    22 
    3   * Fix (i.e. allow / show) name editing on dataset edit. 
    4     * Fix the slugify so it does not overwrite if i change title after fixing name. 
    5     * 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' 
    6   * Show edit summary form again, at least on edit pages (and prefill it for create to something sensible like: Creating dataset {title} {name}) 
     3  * ~~Show edit summary form again, at least on edit pages (and prefill it for create to something sensible like: Creating dataset {title} {name})~~ [Done #1506] 
    74  * ~~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)~~ 
    85    * ~~See also http://lists.okfn.org/pipermail/ckan-discuss/2011-December/001860.html~~ 
    96  * ~~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))~~ [DONE #1506] 
    10   * Merge Groups and Tags into main Edit section (no point having them on their own and most people will miss this). 
    117  * ~~Radically simplify set of licenses~~ [DONE #1359] 
    12   * Clarify that additional info = extra fields + add guidance - #1648 (minor? wontfix?) 
    138  * ~~"Unsaved changes" warning briefly when you click "Save" #1735~~ 
    149  * ~~"Unsaved changed" typo on dataset edit page~~ 
    15   * ~~Force format field to be lower case (with a little bit of javascript!)~~ 
    16    * Why? I think pages like this look nicely formatted: http://thedatahub.org/dataset/1996_population_census_data_canada 
    17    * Shouldn't this be enforced in the commit/validate step of the logic layer rather than JS in the front-end?