There's an inconsistent behaviour between manually updated cantons and updates by scraping.
We aim for empty values, instead of some with zeros.
Looking forward to hearing about constraints and conditions.
Many thanks, a
AFAIK, empty means we don't have info about it from a canton. 0 means we know it is zero from reports.
I.e. many cantons that doesn't have deaths, don't even mention it, but some say it is 0. For this specific field, it is probably good to recommend people to assume 0, if it is empty. I.e. when adding data from multiple cantons, or plotting in time.
For other fields, assuming 0, when it is empty in CSV file is not necessarily correct tho. If the ventilated / intubated numbers is not reported by a canton, we simply don't know if it is 0, or some non-zero number, that just happens to not be reported. Both cases are likely. So the field will be empty to indicate that.
Many thanks @baryluk for your insights. What are yours', @tlorusso @mmznrSTAT ?
I agree with @baryluk . If we have reliant and very clear information that a variable was 0 (e.g. no deceased until date X), we could integrate this. But we might have to provide clear criteria, to ensure that this is handled in a consistent way.
@tlorusso it is quite hard to introduce clear criteria with all the teams invoved here. In the manner of a Scrum Master, I therefore ask: Is it an issue which needs to be solved at all?
And as a Product Owner my answer is: Yes, it does, because some day there will be '0' hospitalizations.
So, I ask you to write down the criteria, and let me know, when done - so that I can inform the manual update/review team.
A team btw which I would ask you to treat with care; most of them are GitHub newbies, and their focus is on data quality. Please respect them, thanks!
I agree with @baryluk and @tlorusso and imho the criteria is very simple: the goal of this repo is to collect and provide data _communicated by the cantons_.
| Value | Meaning |
|---------- | -------------- |
| 0 | they communicated 0 on that date|
|empty | they communicated nothing/did not provide a value for this variable on that date|
Is this something we should add to the Readme to highlight this general rule? If we want this to be clear to everybody we might want to make it as visible as possible @baryluk @andreasamsler @metaodi
Let's add it to the README then.
Most helpful comment
I agree with @baryluk and @tlorusso and imho the criteria is very simple: the goal of this repo is to collect and provide data _communicated by the cantons_.
| Value | Meaning |
|---------- | -------------- |
| 0 | they communicated 0 on that date|
|empty | they communicated nothing/did not provide a value for this variable on that date|