Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dataflow diagram representing conventional annotation data flow among resources #41

Open
pgaudet opened this issue Oct 26, 2022 · 0 comments
Labels
Needs LA approval Needs final approval from the Lead Architect Needs PI Needs PM approval Needs final approval from the Project Manager Needs PO Needs tech doc Needs TL

Comments

@pgaudet
Copy link

pgaudet commented Oct 26, 2022

Project link

TDB

Project description

The purpose of this project is to meet with representatives of various resources (primarily MODS and UniProt) to clearly define which files and formats will be used for data exchange and how that data exchange will take place. The project will be complete when there is a data flow diagram between each of the external resources and the GOC describing which files are used, how they are processes and the timing of the various downloads.

PI

TBD

Project owner (PO)

TBD

Technical lead (TL)

TBD

Other personnel (OP)

TBD

Technical specs

TBD

Other comments

N/A

@kltm kltm added Needs LA approval Needs final approval from the Lead Architect Needs PM approval Needs final approval from the Project Manager Needs tech doc Needs PI Needs PO Needs TL and removed Issue incomplete labels Oct 27, 2022
@pgaudet pgaudet changed the title Coordinating conventional annotation data flow among resources Dataflow diagra representing conventional annotation data flow among resources Apr 30, 2023
@pgaudet pgaudet changed the title Dataflow diagra representing conventional annotation data flow among resources Dataflow diagram representing conventional annotation data flow among resources Apr 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs LA approval Needs final approval from the Lead Architect Needs PI Needs PM approval Needs final approval from the Project Manager Needs PO Needs tech doc Needs TL
Projects
Status: Hopper
Development

No branches or pull requests

2 participants