📝 Document Genomic Data Lifecycle

[dankolbman]

As a member of the Kids First team, I would like to have a place where the genomic data lifecycle processes are documented so that I may have a clear vision of how different systems interact and exchange genomic data.

We should define the data flow with respect to different parts of Kids First to better establish and communicate these lifecycles.

• Genomic data lifecycle conceptual overview page #86 - Genomic Data Lifecycle Overview
  • Document genomic data lifecycle with respect to sequencing centers #79 - Sequencing Centers
  • Document genomic data lifecycle with respect to the data tracker #80 - Kids First Data Tracker
  • Document genomic data lifecycle with respect to the data service #81 - Kids First Data Service
    • Refer to page on Data Service
  • Document genomic data lifecycle with respect to Cavatica #82 - Cavatica
    • Overview Page for Cavatica #87 - Refer to Page on Cavatica
  • Document genomic data lifecycle with respect to PedcBioPortal #83 - PedcBioPortal
  • Document genomic data lifecycle with respect to investigators #84 - Investigators/Researchers

[znatty22]

Is this for documenting the current or future (or both) genomic data life cycle?

This google doc is intended to capture the evolving future genomic data life cycle. Once a design for a particular process is more finalized, I plan to turn it into a README markdown and place it in an appropriate git repo. Then maybe we can link to those in the handbook. Or we could simply include the markdown in the handbook if the handbook is to include future state of our data life cycles 🤷‍♀

[dankolbman]

@znatty22 I think that these pages will serve as a high- to mid-level summary of the genomic data lifecycle. I will work on fleshing out the structure of the different pages and update the issue to demonstrate the different layers.

The doc you linked is very focused on the indexd and dataservice aspect and is very technical. It sounds like a good idea to put this along side whatever codebase is going to responsible for that work and then link it out from the handbook. I'd like to keep something more conceptual and a step or two up in the handbook though.