bcgov / bcgov/bcparks-ar-admin

[A&R Feature Request] Create an API to pull park access advisories into the attendance and revenue system as variances.

Open
#360 1 comment 0 reactions 0 assignees View on GitHub
A&R
Dominant language
TypeScript
Stars
5
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Description: We have a data set of park closures/ access changes run by Rob Fiddler that we would like to pull into A&R as variances. These come from the staff advisory portal & bcparks.ca.

Context: All park access changes and closures affect attendance at parks. They currently need to be added manually as a variance notes but are often missed (POs often think if an area is closed they don't need to add any info for it in the A&R system). Pulling in this data will automate a large percentage of variance notes and help explain data anomolies.

Links to other resources/docs:

Rob's wildfire closure spreadsheet made from an API pulling from CMS. He said he can build us a spreadsheet that includes all closures.

https://bcgov.sharepoint.com/:x:/r/teams/031072/Shared%20Documents/%5BProduct%5D%20bcparks.ca%20(CMS)/Content/Wildfire/BC%20Parks%20Wildfire%20Advisories.xlsm?d=w87565d750c454e9d9a41c141a8691a74&csf=1&web=1&e=Cj4oVf

![image](https://github.com/user-attachments/assets/02fcbd30-769e-4693-9850-ee0625e1a74e)

Staff portal:

https://staff.bcparks.ca/advisories

![image](https://github.com/user-attachments/assets/7e03c6d1-0ddb-4a29-a367-f2b594db52b3)

We would like the advisories to export as variance notes (would show in both regular & variance export), and if possible, be viewable in the data entry screen.

Contributor guide

No contributing guide indexed for this repository

Research direction

No repository files, tests, or entry points are named. Start by examining the staff advisory portal and the CMS closure spreadsheet/API to define the advisory data source and mapping; done means advisories appear as variance notes in both regular and variance exports and, if feasible, in the data-entry screen.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, nodejs, typescript
Domain
backend, backend-api-design, data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.