Open izaslavsky opened 8 years ago
we may also want to keep a log of operations applied to a dataset (eventually, a more full-blown provenance track, but if funded next)
try/catch in the upload module. If it fires - point to a google doc with FAQ at the anchor that says how to deal with wrong CSV (ie pass it through Google sheets) (Sid - for try catch, Ilya for FAQ)
Perhaps leave it till later, or add to FAQ that going through Google Spreadsheet could validate the csv. Also, saving as CSV from Google sheets will keep non-ASCII characters intact