This repository collects feedback sent via the GBIF.org website as Github issues.
From here issues might be moved to their relevant projects (e.g. checklistbank), but most remain here until resolved.
Content, data content and question issues stay in this repository until addressed.
It is our goal that issues in this repository are addressed and closed and no issues remain open.
The user creates an issue and classifies it as well as they can with either: bug, content, question or idea.
The issue is automatically labeled Under review. The Under review is added to avoid spam being exposed on the website and to make sure issues are addressed.
When removing Under review the issue should be labelled according to the area responsible.
The current broad responsibility areas are:
portal: issues that have to do with presentation and bugs in the website.api: issues related to GBIF's APIs (image cache, registry, occurrence, directory etc.), ingestion (crawling, interpreting, indexing) or downloads.data-content: issues with data provided to us by publishers; typically requiring the publisher to resolve them.content: issues with CMS data: text, images, articles, help and so onquestion: helpdesk questionsSo the procedure is:
content issues that are labelled public relevance are public.
The label Pending is used when awaiting a response from the issue reporter, or data publisher.
Since these issues reside in the repo they will probably need more labels. Data content issues can be tagged with a country/region code.
You can change how and how often to be notified of activity here: https://github.com/settings/notifications
See all notifications here: https://github.com/notifications
And ask to be notified by using the eye in the top here: https://github.com/gbif/portal-feedback
You can filter for labels with the usual interface, and you can also exclude labels, for example to see all searches that aren't tagged API or backbone.