Changes between Version 6 and Version 7 of BluePrint/Importer/Excel
- 09/18/13 12:34:14 (10 years ago)
v6 v7 5 5 The limitations of CSV, however, are that there is no client-side Validation or Online Help, so it is very easy for users to input incorrect data (e.g. Dates). 6 6 7 We'd like to allow deployers to build custom Excel workbooks which have protected fields for the core data inputs (like those used for feeding Assessments to the Survey module) and can then add additional Online Help & client-side Validation. They can also be customised more easily for local contexts, such as providing localised names for the Location Hiearrchy rather than 'L1', 'L2', 'L3', etc 8 9 This project, therefore, is about designing a pre-processor for the current Importer back-end to allow .xls files to be uploaded & converting them to CSV before passing them to the current CSV importer. 7 We have now got a pre-processor for the Importer back-end to allow .xls[x] files to be uploaded & converting them to CSV before passing them to the current CSV importer. 10 8 11 9 NB This should also help us with ensuring that imported data is properly UTF-8. MS Excel tends to save CSVs as ANSI whilst it defaults to UTF-8 from 97+ & provides the encoding sed for older versions which can be picked up by xlrd: 12 10 * https://secure.simplistix.co.uk/svn/xlrd/trunk/xlrd/doc/xlrd.html 13 11 12 13 14 15 16 17 18 19 20 21 22 14 23 == Extensions == 15 24 The link to download the template should check for the existence of an .xls in static/formats/s3csv & use that instead of the .csv one where-present.