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

Question

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

simonw opened this issue 3 years ago · comments

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

Simon Willison · Answer 1 · Fri Jun 11 2021 03:33:32 GMT+0800 (China Standard Time)

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

Adrian Edwards · Answer 2 · Sun Jun 27 2021 10:08:14 GMT+0800 (China Standard Time)

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?

Adrian Edwards · Answer 3 · Sun Jun 27 2021 10:11:10 GMT+0800 (China Standard Time)

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

Adrian Edwards · Answer 4 · Sun Jun 27 2021 10:59:20 GMT+0800 (China Standard Time)

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

Adrian Edwards · Answer 5 · Sun Jun 27 2021 11:18:29 GMT+0800 (China Standard Time)

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

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