Closed DSuveges closed 11 months ago
Hi @DSuveges, there are three tickets in the description (#2990, #3026, #3027) which are listed as being either partially or fully assigned to you. Given that I am being responsible for this release from the data team side, I just wanted to double check that the assignment is current and you'll continue to be responsible for those tickets? Or shall I take them over?
23.09
tag pointing to the same commit as the 23.06
release.Data delivered, code updated & all necessary metrics done. The issue is complete.
This is a collection of the data team's tasks for the upcoming 2023 September release. For more context on the priorities of the planned features/updates, see release intention document here. Most data team related issues are in the should/could/won't.
Timeline: The proposed ETL run is expected on the 21th of August. By that time, all data team tasks up to running the parsers, should be completed.
New feature, updates, fixes:
Scope and refactor the baseline expression [@buniello /Data+BE+FE]. Considering how much downstream dependencies this task has, this should be completed soon #3024 . @tskir @bunielloDropped from the 23.09 release following the decision to iterate more by @buniello and @d0choaNew data from Validation Lab in PPP [Data+FE] #2990 We had a meeting with the Validation lab last week, the data is expected to arrive in a few weeks. Given the data, this update has high priority. No schema update is expected. @DSuveges @ehsanb29Dropped from 23.09 release intentions.Association from a new gene burden study could be curated and added to our gene burden dataset. No schema update is expected, however curation repo needs to be updated and released (no ticket yet). @ireneisdoomedI decided not to prioritise this. The study is based on a smaller cohort than what we currently have. It is a systematic analysis, so there were many diseases to map, and the study was anyway not that recent.Moving public CRISPR screen from PPP to public. This task has a trivial, one off solution and a very complex general solution. We need to see what we have time for. No schema change is expected. #2991 @ehsanb29Dropped from 23.09 release intentions.New Project score evidence for PPP #3027. This task might be not too complicated. The new evidence model should either follow the old schema or put something together from the existing fields. So there MIGHT be updates required from the frontend. @ehsanb29 @DSuvegesDropped from 23.09Standard procedures: