Closed kevinschaper closed 10 months ago
It looks like something is up with the join to populate mappings and we're creating these weird mappings when an ID doesn't exist:
example:
HGNC:45103 skos:exactMatch OMIM:<NA> semapv:UnspecifiedMatching HGNC:34495 skos:exactMatch OMIM:<NA> semapv:UnspecifiedMatching HGNC:21224 skos:exactMatch OMIM:<NA> semapv:UnspecifiedMatching
Unfortunately, there are 52k of them, spread out like this:
26730 HGNC -> OMIM 23417 HGNC -> UniProtKB 2692 HGNC -> ENSEMBL 46 HGNC -> NCBIGene
For our current stack, this isn't actually affecting anything since we look up IDs in the object column, and wouldn't look up <NA> (hopefully).
<NA>
resolved in 0.1.5
It looks like something is up with the join to populate mappings and we're creating these weird mappings when an ID doesn't exist:
example:
Unfortunately, there are 52k of them, spread out like this: