Gohelp: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 6: | Line 6: | ||
Actions for person responsible for overseeing tracker: | Actions for person responsible for overseeing tracker: | ||
# Triage queries | # '''Triage queries''' | ||
#* Mark as "accepted" immediately, add additional flags as appropriate | #* Mark as "accepted" immediately, add additional flags as appropriate | ||
#* Assign queries to the person with appropriate expertise. | #* Assign queries to the person with appropriate expertise. | ||
#** This page list GOC's members expertise [https://github.com/geneontology/go-site/blob/master/metadata/group-contacts.csv] to help identify the best people to assign the different queries to. | #** This page list GOC's members expertise [https://github.com/geneontology/go-site/blob/master/metadata/group-contacts.csv] to help identify the best people to assign the different queries to. | ||
# Check the [http://geneontology.org/faq-page FAQ]. Answers might already be there. | # '''Check the [http://geneontology.org/faq-page FAQ].''' Answers might already be there. | ||
#* If needed, improve FAQ documentation on website. | #* If needed, improve FAQ documentation on website. | ||
# Create tickets in other trackers as appropriate. Helpdesk remains open until the query has been addressed. | # '''Create tickets in other trackers as appropriate.''' Helpdesk ticket remains open until the query has been addressed. | ||
#* Ontology, taxon constraints: https://github.com/geneontology/go-ontology/issues | #* Ontology, taxon constraints: https://github.com/geneontology/go-ontology/issues | ||
#* Annotation: https://github.com/geneontology/go-annotation/issues | #* Annotation: https://github.com/geneontology/go-annotation/issues | ||
Line 20: | Line 20: | ||
#* Noctua: https://github.com/geneontology/noctua/issues | #* Noctua: https://github.com/geneontology/noctua/issues | ||
#* Evidence codes: https://github.com/evidenceontology/evidenceontology/issues | #* Evidence codes: https://github.com/evidenceontology/evidenceontology/issues | ||
# Mark tickets as "stale" after ~ 1 month of no response from OP or after a solution has been proposed. Prompt OP for any further related questions; tickets can be closed due to inactivity after a further appropriate amount of time. | # '''Mark tickets as "stale" after ~ 1 month of no response from OP or after a solution has been proposed.''' Prompt OP for any further related questions; tickets can be closed due to inactivity after a further appropriate amount of time. | ||
Revision as of 07:53, 25 February 2019
All GO help queries go to the Github GO Helpdesk tracker
Actions for person responsible for overseeing tracker:
- Triage queries
- Mark as "accepted" immediately, add additional flags as appropriate
- Assign queries to the person with appropriate expertise.
- This page list GOC's members expertise [1] to help identify the best people to assign the different queries to.
- Check the FAQ. Answers might already be there.
- If needed, improve FAQ documentation on website.
- Create tickets in other trackers as appropriate. Helpdesk ticket remains open until the query has been addressed.
- Ontology, taxon constraints: https://github.com/geneontology/go-ontology/issues
- Annotation: https://github.com/geneontology/go-annotation/issues
- AmiGO: https://github.com/geneontology/amigo/issues
- Pipeline: https://github.com/geneontology/go-site/issues
- Rules: https://github.com/geneontology/go-site/issues
- Noctua: https://github.com/geneontology/noctua/issues
- Evidence codes: https://github.com/evidenceontology/evidenceontology/issues
- Mark tickets as "stale" after ~ 1 month of no response from OP or after a solution has been proposed. Prompt OP for any further related questions; tickets can be closed due to inactivity after a further appropriate amount of time.
Review Status
Last reviewed: February 25, 2019