![]() |
Page History
...
Project | Goal | Assigned to | Accomplished? | |
---|---|---|---|---|
1 | ICDC | Data Collection: Acquire C3D-derived data from the COTC010 and COTC018 study | Kevin Burns | Yes |
2 | ICDC | Data Loading: Using Pentaho-based transformations, transform C3D-derived enrollment, Physical Exam, Vital Signs, Extend of Disease, Course initiation, Prior surgery data from the COTC010 & COTC018 study | Kevin Burns | Yes |
3 | ICDC | Create Study, Arm and Cohort records for COTC010 & COTC018 study. | Kevin Burns | Yes |
4 | ICDC | Load case-centric data from the COTC010 & COTC018 study | Kevin Burns | Partial |
5 | ICDC | Create graphQL query API to retrieve programs, studies, studies details, cases, case details,aliquotes, number of samples, number of files, study code, name and number of breeds, name and number of diagnosis, and name and number of genders | Yizhen Chen | Yes |
6 | ICDC | Implement first integration between backend and front end to consume graphQL query API. | Yizhen Chen | Yes |
7 | ICDC | Review and determine constraints around NCATS-related data fields | Philip Musk | Yes |
8 | ICDC | Impose constraints upon NCATS-related fields within ICDC Case, Enrollment, Demographic, Diagnosis, and Samples | Philip Musk | Yes |
9 | ICDC | Impose constraints upon properties within Program and Study | Philip Musk | Yes |
10 | ICDC | Implement Data Loader prototype | Ming Ying | Yes |
11 | ICDC | Replicate Sandbox CI/CD pipeline to Dev Environment | Vincent Donkor | Yes |
12 | ICDC | Implement theme changer, dashboard stats bar and studies view using graphQL API | Ajay Doddapaneni | Yes. Testing is to be done in sprint 6 |
13 | ICDC | Implement K9 site data discalimer | Ajay Doddapaneni | Yes. Testing is to be done in sprint 6 |
14 | ICDC | Mapping all properties to BRIDG entities | Philip Musk | Partial. To be continued in sprint 6 |
Retrospective Results
What went well
Description | Author |
---|---|
We were able to modify the transforms into a NEO4J compliant load, which will also help with consistency moving forward | Kevin |
Teamwork between Phil, Claire, Ming, and I was awesome. We all worked great together | Kevin |
Team collaboration for data collection, and data loading went well (Kevin, Ming, Claire, Phil) | Phil, Ming |
Overall sprint progress was impressive | Todd |
Front end and back end integration to display studies went well | Dimitry, Ajay |
Use of Agile board during stand up meetings helped focusing on ticket progress | Ajay, Afag, Ann |
Transition from one environment to another environment (Sandbox to Dev) was smooth. | Vincent |
GraphQL API integration went well | Yizen |
Team spirit was very high, liked using the Agile board for scrum stand ups to go over the progress of tickets. | Siva |
GraphQL testing went well | Afag |
Team interaction and communication went well | Ann, Amit |
What could have gone better?
Description | Author |
---|---|
Claire, Phil, and I talked about the points on tickets. Some tickets we concluded might need to get a higher point total | Kevin |
Improve UI logistics to improve productivity | Dimitry |
Collaboration and communication with Cloud 1 team is slow and needs improvement | Vincent |
Allocate more QA time | Ye |
Communication regarding data, schema changes, loading and availability of data could be improved | Amit |
Tickets
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|