Open kltm opened 2 years ago
This work is on hold until Tremayne is back from vacation, March 14th.
Issue is some annotation constraints are not encoded in the ShEX and need to be encoded in the tool directly.
Meeting on June 1st to discuss an implementation plan with Tremayne, Kimberly and David.
@balhoff and @kltm will also be there to hammer this out (or give up).
Meeting June 1st to decide how this will get finished.
From the 2023-06-01 meeting, we feel that we need to discuss requirements more fully and compare some concrete proposals for how we want to try to handle the divergence between the ShEx and Noctua annotation conventions.
For now, we can keep as an Active project, but we'd like to discuss this more fully on the next manager's call.
As a technical note from the meeting, we've agreed to stop coding towards any solution until concrete proposal have been put forward and there is general agreement on the way forward.
Moving this back to Requirements because we need to decide on the technical solution for implementation of the extensions in the various workbenches.
Next task is for Kimberly to use the ShEx as a template to see if specs for individual workbenches can be derived from these.
Noting that Seth will be away until mid July (??) so the next discussion on Workbenches call will probably be after that.
Project link
https://github.com/orgs/geneontology/projects/175
Project description
Work to add more annotation extensions relations and constraints on their usage to the Noctua form and pathway editors.
PI
PaulT
Project owner (PO)
Kimberly
Technical lead (TL)
Seth
Other personnel (OP)
David, Dustin, Tremayne, Jim
Technical specs
(WIP) https://docs.google.com/document/d/10lw_6OQF0XOVhInkZoJiRnBlR_m-mGqByb9DtRn_LYQ We got ahead of ourselves here, but no further technical discussion should be needed (2022-12-01 go software discussion)
Other comments
N/A