Suggestions for Briefcase CSV

[getodk-bot]

Issue by mitchellsundt
Thursday Jul 09, 2015 at 17:49 GMT
Originally opened as getodk/getodk#218 (1 comment(s))

---

Originally reported on Google Code with ID 217

From Manna Energy

null fields show in the briefcase csv as nothing so you end up with a bunch of commas
in a row when there is a null value from an optional field that was skipped. This,
combined with the fact all the other fields with values have quotation marks, makes
it difficuilt to parse the csv via delimiters. Cant use commas because those can be
in the strings as well, but you cant use "," either because the null fields are lacking
quotes. We had to resort to some craftyness to properly delimit the csv. 

Reported by wbrunette on 2011-05-20 22:13:03

[getodk-bot]

Comment by mitchellsundt
Thursday Jul 09, 2015 at 17:49 GMT

---

There's actually an RFC describing CSV file formats.  
The complaints are a critique of the CSV file format, which Briefcase adheres to:

http://tools.ietf.org/html/rfc4180

Changing to documentation.

Reported by mitchellsundt on 2012-01-30 22:04:05

• Labels added: Type-Other, Documentation
• Labels removed: Type-Defect