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

Discuss and create roadmap for integrating remaining resource upstream files #42

Open
kltm opened this issue Oct 27, 2022 · 6 comments
Open
Assignees
Labels

Comments

@kltm
Copy link
Member

kltm commented Oct 27, 2022

Project link

https://github.com/orgs/geneontology/projects/109

Project description

Start creating a roadmap and timeline for pulling remaining upstream files to me processed directly into the GO Central pipeline.

This is to be coordinated at some extent with the Alliance.

Deliverables should be:

  • An understanding of what files remain in upstream resources
  • An understanding of the kinds of software being used at the MODs for the processing of these files
  • A feel for how well this software generalizes across upstream resources
  • An agreement that if we could do this processing, resources could go "all-in" with Noctua and GO Central as the source for all functional annotation; i.e. GO would have no upstream pickups from participating resources.
  • An outline of a timeline to complete the transition to GO being able to fully absorb a resource (bring in or create software, add to pipeline, integrate into data products)

Performing these tasks is not a deliverable.

PI

@cmungall

Project owner (PO)

@ukemi

Technical lead (TL)

@kltm

Other personnel (OP)

TBD

Technical specs

No technical specs needed as the only product is discussion and the creation of requirements. That said, we are indeed planning this out, so we decided a non-active tech doc would be useful:
https://docs.google.com/document/d/10m5ZQ6ffugaUb2L85TtBB94-5G12GwVH9b8JjO_4Y6Y/edit
This may eventually evolve into the final tech doc.

Other comments

N/A

@kltm
Copy link
Member Author

kltm commented Oct 27, 2022

@pgaudet Not sure if this is "Hopper" or "Priority"...

@kltm kltm added Needs PM approval Needs final approval from the Project Manager Needs PI Needs PO and removed Issue incomplete labels Oct 27, 2022
@pgaudet pgaudet moved this from Hopper to Priority (project triage) in Project Metadata Overview Dec 13, 2022
@pgaudet
Copy link

pgaudet commented Dec 13, 2022

  • PI call 2022-12-13 Proposal: take data GOA + data from MOD and compile this data as a curated annotated file

@pgaudet pgaudet moved this from Priority (project triage) to Resourcing (assign PI, PO, TL, staff) in Project Metadata Overview Feb 15, 2023
@pgaudet pgaudet removed the Needs PM approval Needs final approval from the Project Manager label Feb 22, 2023
@pgaudet pgaudet moved this from Resourcing (assign PI, PO, TL, staff) to Active in Project Metadata Overview Feb 22, 2023
@pgaudet
Copy link

pgaudet commented Feb 22, 2023

Next goal: concrete proposal for the GOC meeting

@pgaudet
Copy link

pgaudet commented Mar 22, 2023

Next step: David, Seth, Chris to meet to make a concrete plan as to how to move forward

@kltm
Copy link
Member Author

kltm commented Mar 23, 2023

Planned for April 7th.

@pgaudet pgaudet moved this from Active to Resourcing (waiting for capacity) in Project Metadata Overview May 24, 2023
@pgaudet
Copy link

pgaudet commented May 24, 2023

Putting back into Resourcing until we have someone to go this.

@ukemi Please comment if this not reflecting what is happening.

@pgaudet pgaudet moved this from Resourcing (waiting for capacity) to Hopper in Project Metadata Overview Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Hopper
Development

No branches or pull requests

3 participants