goci
goci copied to clipboard
Mapping Pipeline - Story Ensembl history to avoid mapping being removed when Ensembl gives empty response
Currently Mapping pipeline makes a call to Ensembl every time & removes the existing mapping from DB , Ensembl sometimes gives empty mapping response & this leads to missing mapping information in DB , we need to store Ensembl response history in DB to avoid making new call for already mapped variants