Repository navigation
Conversation
|
|
||
| For service outages, check the [B.C. Data Catalogue status page](https://catalogue-status.data.gov.bc.ca/), which includes monitoring for WMS and WFS GetCapabilities requests. | ||
|
|
||
| For catalogue or web mapping support, use the [Data Systems & Services support portal](https://dpdd.atlassian.net/servicedesk/customer/portal/1). Select "Data Requests" for catalogue support or "Web Mapping Requests and Services" for web mapping support. |
There was a problem hiding this comment.
| For catalogue or web mapping support, use the [Data Systems & Services support portal](https://dpdd.atlassian.net/servicedesk/customer/portal/1). Select "Data Requests" for catalogue support or "Web Mapping Requests and Services" for web mapping support. |
There was a problem hiding this comment.
I suggest we not route users through the the API team.
There was a problem hiding this comment.
We only get a handful (or less) of issues related to API outages per year and I think the trade-off of us handling those issues is a better balance versus adding the cognitive load to users to understand if their issue is the API service or bcdata and then to figure out where to log an issue.
|
|
||
| For service outages, check the [B.C. Data Catalogue status page](https://catalogue-status.data.gov.bc.ca/), which includes monitoring for WMS and WFS GetCapabilities requests. | ||
|
|
||
| For catalogue or web mapping support, use the [Data Systems & Services support portal](https://dpdd.atlassian.net/servicedesk/customer/portal/1). Select "Data Requests" for catalogue support or "Web Mapping Requests and Services" for web mapping support. |
There was a problem hiding this comment.
We only get a handful (or less) of issues related to API outages per year and I think the trade-off of us handling those issues is a better balance versus adding the cognitive load to users to understand if their issue is the API service or bcdata and then to figure out where to log an issue.
Co-authored-by: Stephanie Hazlitt <stephanie.hazlitt@gov.bc.ca>
Co-authored-by: Stephanie Hazlitt <stephanie.hazlitt@gov.bc.ca>
This branch has not been deployed
2 participants
Reverts #374 which reverted #340. Too quick of a merge.