Version 7 (modified by Fran Boon, 10 years ago) ( diff )

Back-end ready, focus on front-end

Import Excel

We have an Importer which uses CSV files and works very well when the correct data is entered.

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).

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.

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:


We would like default Excel Workbooks for all of our major resources which have protected fields for the core data inputs (like those used for feeding Assessments to the Survey module).

We would like some Excel routines for:

  • Date[Time] Validation
  • Selection from pre-populated dropdowns
  • Selection of Location Hierarchy
  • Online Help

Deployers can then customise the default Excel workbooks for local contexts, such as providing localised names for the Location Hierarchy rather than 'L1', 'L2', 'L3', etc and prepopulating the spreadsheet with a valid lookup lists.


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.

Note: See TracWiki for help on using the wiki.