GO-CAM November 22, 2017: Difference between revisions
Jump to navigation
Jump to search
Line 46: | Line 46: | ||
== Updates/Discussion on 1.0 Release Milestones == | == Updates/Discussion on 1.0 Release Milestones == | ||
=== Annotation Attribution in GPAD Output Files === | === Annotation Attribution in GPAD Output Files === | ||
*Seth will implement a Jenkins job that checks, for all entries in users.yaml that have edit permission in Noctua, | *Seth/Berkeley will implement a Jenkins job that checks, for all entries in users.yaml that have edit permission in Noctua, | ||
**there exists an orcid | **there exists an orcid | ||
**there exists at least one group (that is also present in groups.yaml?) | **there exists at least one group (that is also present in groups.yaml?) |
Revision as of 13:41, 22 November 2017
Zoom URL
https://stanford.zoom.us/j/679970729
Agenda
Updates/Discussion on 1.0 Release Milestones
Annotation Attribution in GPAD Output Files
- noctua github ticket #458 - Attribution with GO-CAM exports to GOC annotation files
- noctua github ticket #502 - providedBy should be used in GPAD export
- go-site github ticket #453 - All Noctua curators should have "updated" metadata associated in the YAML file (including group and URI)
- Issue summary: we want to make sure that, in the GPAD files, attribution in the 'Assigned By' field is correctly populated with a curator's annotation group
- Is this a good time to clean house wrt older or test models?
- Step 1: Curators need to have entries in the groups field of the users.yaml file
- Some groups still need to review their users.yaml (i.e. they are missing groups and also sometimes even missing orcids):
- USC
- UniProt (SIB and EBI)
- PomBase
- FlyBase
- SynGO
- Xenbase
- Groups that are okay:
- BHF-UCL
- dictyBase
- MGI
- SGD
- TAIR
- WB
- Zfin
- Some groups still need to review their users.yaml (i.e. they are missing groups and also sometimes even missing orcids):
- Step 2: Convert any remaining GOC:nn identifiers to orcids
- Step 3: Determine if, for any models, curators would not want their default groups to be used to populate providedBy value
- Step 3: Populate providedBy value with appropriate group for each evidence statement 'Contributedby' a given curator
- Step 1: Curators need to have entries in the groups field of the users.yaml file
- Question: What is the significance of the model-level providedBy and how is it populated?
Display user and group labels from minerva metadata
Allow negation in Noctua and SAE and in GPAD export
export-lego-to-gpad-sparql should collate by MOD
MInutes
- On call: Barbara, Chris, Edith, Harold, Jim, Kevin, Kimberly, Pascale, Paul T., Sabrina, Seth, Suzi
Agenda
Updates/Discussion on 1.0 Release Milestones
Annotation Attribution in GPAD Output Files
- Seth/Berkeley will implement a Jenkins job that checks, for all entries in users.yaml that have edit permission in Noctua,
- there exists an orcid
- there exists at least one group (that is also present in groups.yaml?)
- Entries in users.yaml file that don't meet these requirements will be output in the Jenkins report and users will be asked to update
Display user and group labels from minerva metadata
- Changed from 1.0 Milestone to wishlist as this impacts the contributor display on the landing page and is not essential for curation or GPAD output
Allow negation in Noctua and SAE and in GPAD export
export-lego-to-gpad-sparql should collate by MOD
- Will be implemented imminently