[openspending-dev] Data upload failed

[Gregor Aisch]

Also, generally spoken, when designing a system for uploading data, I'd always prefer the try-to-read-everything strategy over forcing (inexperienced) users to convert data to some nerdy RFC standards. In fact, 80% of our users will not try to upload their data again after facing an error message like "sorry, but your data is not in the right format (=you suck). please read the RFC 4180 for more details (=just give it up, stupid).".

I really love how Refine handles data imports.



Am 05.02.2012 um 00:24 schrieb Friedrich Lindenberg:

> Hey Gregor,
> 
> thanks for trying this but I'm not sure we want to support this - I've
> actually limited the set of things messytables will do in OpenSpending
> intentionally because I think that when data is handed to OS, it
> should already be formatted properly (which includes using actual
> CSV).
> 
> I'll soon have to do a lot of fixes against messytables for the DGU
> spend, but suspect enabling all this in OpenSpending may actually lead
> to more ambiguity than just having a clear rule
> (http://tools.ietf.org/html/rfc4180)
> 
> What do you think?
> 
> - Friedrich
> 
> On Sat, Feb 4, 2012 at 6:42 PM, Gregor Aisch <gregor.aisch at okfn.org> wrote:
>> Tried to upload some spending data to openspending to find out that the
>> automated CSV recognition failed to detect the tab-separated table..
>> 
>> Seems to be a bug in messytables so I added a new issue. Who's maintaining
>> that package?
>> 
>> https://github.com/okfn/messytables/issues/3
>> 
>> 
>> 
>> _______________________________________________
>> openspending-dev mailing list
>> openspending-dev at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/openspending-dev
>> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/openspending-dev/attachments/20120205/a8ccbc7a/attachment.html>