biggtfish / google-refine

Automatically exported from code.google.com/p/google-refine
Other
0 stars 0 forks source link

Export CSV without replacing null values with double quotes? #611

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I am attempting to export my data as a CSV file. But every value in my table 
that is blank is being replaced by "" when I export it.

I would like the option to have nothing, so it would just look like:

data, data, data,, data, data,, data

and so on. Where the ,, represents a blank cell.
Instead, this is what I am getting:

data, data, data, "", data, data, "", data

It is replacing the empty cells with double quotes, and I do not want this.

Is there a way to change the settings some how? So it will just leave a blank 
cell blank.

Original issue reported on code.google.com by Austen....@gmail.com on 17 Sep 2012 at 9:00

GoogleCodeExporter commented 8 years ago
Issue 612 has been merged into this issue.

Original comment by tfmorris on 17 Sep 2012 at 10:28

GoogleCodeExporter commented 8 years ago
Does this happen independent of whether you ask for strings to be quoted on 
output?  Are the cell values that you're attempting to output nulls or empty 
strings ("")?

Original comment by tfmorris on 18 Sep 2012 at 3:33

GoogleCodeExporter commented 8 years ago
So it turns out the person who was inspecting the CSV files I sent her was 
getting them backwards. Google Refine was outputting them with just ,, for a 
blank cell. The data we imported to GR before had the ,"",  But GR turned them 
into ,,

So I think this is a non-issue at this point.

But can you tell me where I would ask for strings for to be quoted on output 
like you mentioned? I can't find settings like that anywhere.

Original comment by Austen....@gmail.com on 18 Sep 2012 at 3:40

GoogleCodeExporter commented 8 years ago
Thanks for the update.  I'll close this.

As far as the output option, I was apparently misremembering the input option 
which controls quote handling.  On the output side we always follow the spec.

Original comment by tfmorris on 18 Sep 2012 at 4:06