Skip to content

More "bad nulls" (from email) #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
onyxfish opened this issue Dec 17, 2015 · 0 comments
Closed

More "bad nulls" (from email) #14

onyxfish opened this issue Dec 17, 2015 · 0 comments

Comments

@onyxfish
Copy link
Contributor

Copying over from emailed note

I did want to add to your ‘Zeros replace missing values’; in my time as an ETL developer (before going back into academia) I have come across the following as common entries for missing values:

-1
99
...
-99999
...
-99
00000

Basically, stuff the field with as many 9s as it will hold or, if possible, make it negative as that is ‘clearly’ a non-sensical value. Never bother documenting any of these decisions. I’ve actually never come across 0 for missing, but that might be the type of data I work with. Point being, I would suggest emphasising that distributions and summaries, as well as specific tests on each row for ‘reasonableness’ (e.g. ‘break if {value} < 0’), are a key part of most processing and analysis regardless of the quality of the data itself.
@onyxfish onyxfish changed the title More "bad nulls" (from email More "bad nulls" (from email) Dec 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant