Skip to content
This repository has been archived by the owner on Jun 1, 2022. It is now read-only.

Investigate 59 locations where vaccinefinder:xxx differed from vaccinefinder_org:xxx #656

Open
simonw opened this issue Jun 10, 2021 · 5 comments
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
Copy link
Collaborator

simonw commented Jun 10, 2021

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 the vaccinefinder_org:xxx concordance (or possibly from the vaccinefinder_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=vaccinefinder

Or here: https://vial.calltheshots.us/api/searchLocations?authority=vaccinefinder&format=map&all=1

@simonw 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
@simonw
Copy link
Collaborator Author

simonw commented Jun 10, 2021

Not sure if this matters or not. Leaving the issue open for the moment.

@MoralCode
Copy link

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?

@MoralCode
Copy link

i did notice that at least one of the records (recWqoMmBXBUDnS4z) affected by this issue was also affected by #696.if that means anything

@MoralCode
Copy link

MoralCode commented Jun 27, 2021

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):

select
    concordance_identifier.authority,
      concordance_identifier.identifier,
    location.id,
    'https://vial.calltheshots.us/location/' || location.public_id as view_url,
    location.name,
    location.full_address
from concordance_location join concordance_identifier on concordance_location.concordanceidentifier_id = concordance_identifier.id join location on concordance_location.location_id = location.id join report on location.dn_latest_non_skip_report_id = report.id
where
  concordance_identifier.authority = %(authority)s AND location.id != report.location_id

@MoralCode
Copy link

MoralCode commented Jun 27, 2021

Full list of locations that are affected by both this and the mapbox issue (assuming my query is accurate):

https://vial.calltheshots.us/location/recvf9dTRHgHZiHkR
https://vial.calltheshots.us/location/rec5Sg0lmi9MRs8to
https://vial.calltheshots.us/location/recVUHuB3bbhpqwY0
https://vial.calltheshots.us/location/lfczh
https://vial.calltheshots.us/location/recNUwfgdagkPMa6l
https://vial.calltheshots.us/location/recWqoMmBXBUDnS4z
https://vial.calltheshots.us/location/recbpeLJzvRuak1q2
https://vial.calltheshots.us/location/recAuviAO4C5ukkcb
https://vial.calltheshots.us/location/ldkkp
https://vial.calltheshots.us/location/rec8oG4y6cgDLQSxq
https://vial.calltheshots.us/location/recYexkMhSXkrzUWL
https://vial.calltheshots.us/location/rech5w8fbSlS6qLCF
https://vial.calltheshots.us/location/recTzYPYxTFkYzRjF
https://vial.calltheshots.us/location/rec4HMauRp1jIA9T5
https://vial.calltheshots.us/location/recSNFTlLMEkncecP
https://vial.calltheshots.us/location/rec47LhdhHJhhFgFq
https://vial.calltheshots.us/location/rec22nN3WTAI0hwGp
https://vial.calltheshots.us/location/recYA30XLXT6zSchH
https://vial.calltheshots.us/location/recQY7j3pexObXbxv
https://vial.calltheshots.us/location/recfkGYoWvDu4GWGO
https://vial.calltheshots.us/location/recgHEpysqJ41TEU4
https://vial.calltheshots.us/location/recbECvQlveAyBorV
https://vial.calltheshots.us/location/lfctz

https://vial.calltheshots.us/dashboard/?sql=select%0D%0A++++concordance_identifier.authority%2C%0D%0A++++++concordance_identifier.identifier%2C%0D%0A++++location.id%2C%0D%0A++++%27https%3A%2F%2Fvial.calltheshots.us%2Flocation%2F%27+%7C%7C+location.public_id+as+view_url%2C%0D%0A++++location.name%2C%0D%0A++++location.full_address%0D%0Afrom+concordance_location+join+concordance_identifier+on+concordance_location.concordanceidentifier_id+%3D+concordance_identifier.id+join+location+on+concordance_location.location_id+%3D+location.id+join+report+on+location.dn_latest_non_skip_report_id+%3D+report.id%0D%0Awhere%0D%0A++concordance_identifier.authority+%3D+%25%28authority%29s+AND+location.id+%21%3D+report.location_id%3AsMCSQpgWL9OJ5xTiS2xHTe6XhwGfCoGRgBpFTe0RMXI&authority=vaccinefinder

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
Projects
None yet
Development

No branches or pull requests

2 participants