Re: #correspondencetables header format #correspondencetables
When I tried to create metadata yesterday for one of the tables (isic4 to Nace2 I think) that table was in the format you describe. The problem was that some columns had mixed data types (e.g. strings and numbers) and the infer function got it wrong so I had to manually fix this. So I would suggest to keep data types homogeneous within the same column – if possible!
Not sure how to deal with missing values but I don’t think using e.g. zero is a good option so I would also go for empty value. OK for separator and header.
From: <firstname.lastname@example.org> on behalf of "miguel.astudillo via Groups.Io" <miguel.astudillo@...>
For consistency I think we should specify a bit more the format of the final tables
Separator: I’d propose “,”
null values: An empty value seems reasonable to me, but I do not have a strong preference.
Header: just one row, the first one
That should help the parser later on. What do you think?
From: email@example.com <firstname.lastname@example.org> On Behalf Of michele.derosa@...
Sent: 25 March 2019 18:21
Subject: Re: [hackathon2019] #correspondencetables header format
Agree. Isn t this also the current format of the tables?