This repository has been archived by the owner on Jun 1, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Investigate 59 locations where vaccinefinder:xxx differed from vaccinefinder_org:xxx #656
Labels
bad-data
Data that looks bad and needs investigating, or tasks to clean up bad data
help wanted
Extra attention is needed
Comments
simonw
added
bad-data
Data that looks bad and needs investigating, or tasks to clean up bad data
help wanted
Extra attention is needed
labels
Jun 10, 2021
Not sure if this matters or not. Leaving the issue open for the moment. |
What would be the desired solution to this issue? is the goal to find out what caused this to happen? fix the records? remove the offending concordances? |
i did notice that at least one of the records (recWqoMmBXBUDnS4z) affected by this issue was also affected by #696.if that means anything |
recbpeLJzvRuak1q2 and lfczh are also affected by both issues. stil not sure if they are related though here is what i suspect is a query to show all the locations that are affected by both (i dont yet have permisson to run it though so idk how valid it is):
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bad-data
Data that looks bad and needs investigating, or tasks to clean up bad data
help wanted
Extra attention is needed
Found these while working on #555 - there are 59 locations (excluding those that are soft deleted) where they had a
vaccinefinder:xxx
concordance that different from thevaccinefinder_org:xxx
concordance (or possibly from thevaccinefinder_location_id
database column).I left the
vaccinefinder
tag on them so we could look at them later. Here they are: https://vial.calltheshots.us/dashboard/concordances-by-authority/?authority=vaccinefinderOr here: https://vial.calltheshots.us/api/searchLocations?authority=vaccinefinder&format=map&all=1
The text was updated successfully, but these errors were encountered: