In cases where a previous mapping job has populated the target_gene.uniprot_id_from_mapped_metadata value, a subsequent mapping job may not result in a UniProtID value. In theses case the existing value can remain in this field when target_gene fields are updated, resulting in a mismatch that would not occur in a new target_gene record.
To prevent this, the uniprot_id_from_mapped_metadata field should be cleared when a target_gene is being updated as part of the map_variants_for_score_set function, and prior to running UniProt ID mapping.
In cases where a previous mapping job has populated the
target_gene.uniprot_id_from_mapped_metadatavalue, a subsequent mapping job may not result in a UniProtID value. In theses case the existing value can remain in this field whentarget_genefields are updated, resulting in a mismatch that would not occur in a newtarget_generecord.To prevent this, the
uniprot_id_from_mapped_metadatafield should be cleared when atarget_geneis being updated as part of themap_variants_for_score_setfunction, and prior to running UniProt ID mapping.