EBISPOT / gwasdepo-deposition-service

0 stars 1 forks source link

Deposition - Store Analysis software field in DB #239

Closed sajo-ebi closed 6 months ago

sajo-ebi commented 7 months ago

Currently the metadata template contains Analysis software field which is not captured in DB , we need to store this in DB as this filed is required in Sumstats metadata Yml , this will need changes in Deposition service, template validator & Ingest service for metadata Yml API call.

ljwh2 commented 7 months ago

@jiyue1214 to provide list of GCSTs and analysis software - this info was captured from old-style yaml files, not available in new-style ones

jiyue1214 commented 7 months ago

GCST and available analysis_software: https://docs.google.com/spreadsheets/d/1sBdGFXZd2dZxIkO_BpDS44QV_Bqv2HWmmD6xDpQQrso/edit#gid=0

ljwh2 commented 7 months ago

@sajo-ebi to discuss with @karatugo best approach to populate DB with analysis SW for these GCSTs

ljwh2 commented 6 months ago

@sajo-ebi to create new ticket to populate old values and close this one

sprintell commented 6 months ago

This is now tracked here: https://github.com/EBISPOT/gwasdepo-deposition-service/issues/242

jiyue1214 commented 5 months ago

I updated the analysis software I can acquire from all yaml files: 7_Feb: I extracted analysis_software field from all yaml files before any regeneration on 7th Feb 30_Apr: I extract analysis_software field from all yaml files on the staging folder on 30th Apr

jiyue1214 commented 5 months ago

Question: Do I need to check the user submission forms from Feb to Apr to see if any analysis_software is missing in the yaml file?