UX improvements to dataset edit as of Dec 2011

[rgrp]

Super ticket: #1506

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