sajo-ebi
sajo-ebi
We need to analyse the Submission Id '6317b82037db2600015a836c' which had the studies mapped with risk allelle & Snp 'rs36083960'. This was causing the DR Purge job to fail , currently...
Deposition Sync currently runs on the Crontab in VM , we need to make it trigger through Spring scheduler to avoid dependancy on VM Cron
As part of releasing Traits Functionality we have to deploy following components to Production -: gwas-curation-service gwas-ingest-service gwas-curation-ui Goci There are some steps which need to be done post deployment...
There was an issue in Python script where we got the following error -: ``` [INFO] Database connection to SPOTREL was successful [Warning] Number of studies do not match. Traceback...
As part of investigating issue [https://app.zenhub.com/workspaces/gwas-59df823c4a6feb3786810391/issues/gh/ebispot/goci/1218](https://app.zenhub.com/workspaces/gwas-59df823c4a6feb3786810391/issues/gh/ebispot/goci/1218) we have found that the studies for 2 submissions '6504680ce6cd8200013a05f6' and '5f697cd6a54daa00013cf263' have been duplicated . As part of resolution we plan to reupload...
At the moment Depo Sync only creates unpublished studies when a body of work submission is created via Deposition app, but if the submission is edited via Depo CUration then...
Sumstats FTP sync is failing is because of accession Id being null returned from Public studies API , we had changed API to return all studies instead of isPublished flag...
The fallback servers are not reflecting the latest DR & need manual execution of Fallback Symlinks & Solr refresh in order to reflect latest data changes
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...