Extend GO API to include basic access to GO-CAMs using new abstraction #99
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
Project link
https://github.com/orgs/geneontology/projects/225
Project description
There are currently two exposed ways to access GO-CAM information in the GO API. The first is (mostly) using the complicated abstraction that Noctua itself uses, which is too complicated for end users. The second is a somewhat suboptimal abstraction that was designed for the GO-CAM site.
Details still in discussion:
https://docs.google.com/document/d/1h_vnzkP94YC5l3ZmxKyZVOuTzIHIsHRsOLtBSGyB25k/edit?tab=t.0
https://docs.google.com/document/d/1GzTnSY10pWDzvceM5p0Dx6AV1KFAl9thRr2VgjWJCVc/edit?tab=t.0
Scope/Deliverables
Motivations
Coordination (with other resources)
Tasks
TBD
Dependencies
None
Cost/Resources
1M? However, Sierra is partial, so it is expected to take a little time.
Strengths/Opportunities
TBD
Weaknesses/Threats
Risks/Mitigations
TBD
Fail state/Withdrawal
Technical specs
TBD (template: https://docs.google.com/document/d/111UqtS3G0aJZpAijZYI3Da0t94OQpGePlPJsqZE4Tio/edit)
Personnel
PI: Chris; PO: Pascale; TL: Sierra
Other comments
N/A
The text was updated successfully, but these errors were encountered: