http://localhost/ticket/205 <p> Importer function is exposed to logged in users. </p> <p> Alongside specifying file to import, user chooses between 'form schemas' - 'basic' and 'government'. </p> <ul><li>Basic is as it is currently </li><li>Government form has pre-defined Extra fields, careful validation of lots of fields, code formats/processes some field data for storage. e.g. searching for tag keywords. </li></ul><p> All fields should be in step with the government custom input form. </p> <p> For fields which have suggested values but the user can input his own value, this is achieved in the spreadsheet with two columns - the first being a drop-down and the second free text. </p> <p> Estimate: </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/205 Trac 0.12.3 rgrp Mon, 07 Feb 2011 08:47:30 GMT http://localhost/ticket/205#comment:1 http://localhost/ticket/205#comment:1 <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>wontfix</em> </li> </ul> <p> wontfix as: </p> <ol><li>Easier to just to an import from google docs for which we have several importer examples in ckanclient </li><li>(More important) importing is something that is quite bespoke (changes for each cirumstance). As a result pre-written importers tend to be very fragile and it is not a good use of time to try and some customizable WUI one when you can just write a custom importer in code (code is much more flexible than whatever we can write!) </li></ol> Ticket