Annotation Conf. Call 2017-12-12: Difference between revisions
Jump to navigation
Jump to search
Line 5: | Line 5: | ||
== Infrastructure == | == Infrastructure == | ||
*[http://skyhook.berkeleybop.org/snapshot/metadata/users-and-groups-report.txt Report on missing orcids and groups in users.yaml file] | *[http://skyhook.berkeleybop.org/snapshot/metadata/users-and-groups-report.txt Report on missing orcids and groups in users.yaml file] | ||
*Please keep in mind that the report is generated as part of the new build and a new attempt is made every night. | |||
*This means that: | |||
** 1) if the load fails the report may not be there (which is a good thing) | |||
** 2) there will times every day during regeneration when the report is not yet there | |||
== github review == | == github review == |
Revision as of 11:20, 7 December 2017
Meeting URL
Agenda
Infrastructure
- Report on missing orcids and groups in users.yaml file
- Please keep in mind that the report is generated as part of the new build and a new attempt is made every night.
- This means that:
- 1) if the load fails the report may not be there (which is a good thing)
- 2) there will times every day during regeneration when the report is not yet there
github review
- go-annotation tracker is used for issues and project management related to the annotation working group
- Issues:
- Annotation review
- PAINT family review
- Keyword mapping questions
- Questions about annotation practice
- Proposals for annotation guidelines
- Requests for annotation rules
- Requests for documentation
- Use of labels
- Please always add a label to your issue
- Trying to simplify the list of labels
- Removed some that were overlapping, not applicable to this repo
- Would like to move from using group labels to tracking submission via author
- is:issue author:vanaukenk
- All curators who need to work on an issue should be listed in the Assignee field
- Remove your name from the list when you've addressed or complete the work