http://localhost/ticket/972 <p> Rather than have a separate 'extras' key all the extras fields should be consolidated into the main package dict when presenting the package internally or e.g. via the API. </p> <p> Why? Extras are really just an artefact of our internal storage model. Clients of the system (both internal and external) should just see a set of key/values with no distinction between extras and non-extras. </p> <h2 id="Issues">Issues</h2> <ul><li>Possible breaking change to the API (could enforce backwards compatibility by keepings extras for the time being) </li></ul><p> Possible subticket of forms refactoring: <a class="closed ticket" href="http://localhost/ticket/961" title="enhancement: [super] Refactoring of forms, validation and model synchronization (closed: fixed)">#961</a> </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/972 Trac 0.12.3 thejimmyg Tue, 15 Mar 2011 20:05:09 GMT http://localhost/ticket/972#comment:1 http://localhost/ticket/972#comment:1 <p> I don't really agree with this. In fact I'd rather move further away from auto-magic key value pairs stored in <a class="missing wiki">JsonTypes?</a>. Can we discuss on Skype please? </p> Ticket thejimmyg Fri, 08 Jul 2011 14:08:49 GMT http://localhost/ticket/972#comment:2 http://localhost/ticket/972#comment:2 <ul> <li><strong>repo</strong> set to <em>ckan</em> </li> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>theme</strong> set to <em>none</em> </li> <li><strong>resolution</strong> set to <em>wontfix</em> </li> </ul> <p> Having thought about this more David Raznick and I have decided to stick with separate extras for the timebeing. Mainly because of internationalisation issues. </p> Ticket