Closed ingonader closed 2 years ago
Thanks. This appears to be an error in our data release workflow @timothymodel @cwang23
Yup, there's a bug somewhere in the cleanQualtrics or the public release script that's causing that...
I'm working on another issue today.
Would you be able to take a look at this @Nikola Danevski ndanevsk@u.rochester.edu and @Wong, Brian bwong526@wharton.upenn.edu?
Thanks, Tim
On Tue, Jun 23, 2020 at 6:32 AM Robert Kubinec notifications@github.com wrote:
Thanks. This appears to be an error in our data release workflow @timothymodel https://github.com/timothymodel @cwang23 https://github.com/cwang23
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/saudiwin/corona_tscs/issues/14#issuecomment-648149966, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIVDDS6RLIF7PDKMNQGVT3LRYCVHRANCNFSM4OFTSGEQ .
Hi, I am checking if this is up to date, and I have checked that there are still records where the date_start is later than the date_end, which generates a negative policy duration. I have checked the initial_data and qualtrics_afterfill files, which generate 1360 records in both files, in the case of internal_data, there are 550 records. I have also done some manual tests on the shinyapp to confirm this. Thanks! Isaac.
Please note that this problem should not grow over time, there are checks put in place now which prevents this problem from occurring and we are actively making progress to clean existing policies with this issue.
For a few
record_id
s, thedate_start
is later then thedate_end
, which would indicate a negative duration of that policy. This is the case for the followingrecord_id
s:Example:
An R code snippet to find this data: