Closed pwalsh closed 9 years ago
@pwalsh what do we need to fix this - about 50% of files i test from UK spend files get this error and it ain't very informative ;-)
It shouldn't be much work (a few hours including tests). From my experience, the UK data is the encoding issue, as I mentioned here: https://github.com/okfn/goodtables-web/issues/41#issuecomment-106196131
@pwalsh great. Let's do it. Can we detect encoding in goodtables better? (or given this come from spend dashboard should we compute encoding when we scrape files and be using that in the url).
Also is this something for Artem or just you?
Encoding is either chardet (https://github.com/chardet/chardet) for automatic, or an explicit string from the user. Yes, we could probably get it from the headers on the data.gov.uk server, presuming they are correct, as a third option.
Artem is full this week: I could do it or he could. There are a few good tables issues now - it is just a matter of priority. I need all day tomorrow on census, and some OS. I can do a round on Good Tables on Thursday, first doing the UI of results, and then this. WDYT?
Thursday sounds good. I'd say this + GET item is more important than the UI item which we can do last.
At least make sure that specific error messages are shown to the user.