This ticket is to enable sysadmin users of A&R to export a report of all parks and subareas within the A& system so they can use it as reference - making A&R source of truth for subarea data and removing the need for us to keep the other excel spreadsheet up to date.
If subareas are added or changed this will happen using BRS-897: Add Park/Subarea POST/PUT functionality and then users can see a full list via this export.
CSV export should have the following fields (similar to the existing excel doc). Each row is a sub area.
ORCS Number
Park
Region
Section
Management Area
Bundle
Sub Area ID
Park Sub Area
Frontcountry Camping (yes/no)
Backcountry Camping (yes/no)
Group Camping (yes/no)
Day Use (yes/no)
Boating (yes/no)
Frontcounty Cabins (yes/no)
Backcountry cabins (yes/no)
Acceptance Criteria:
User can export a csv showing all subareas and their related park and activities
Export report page is unavailable to non-sys admin users and we can leave that as-is for this report - ie. only sysadmin users can technically get to that page anyways
CSV with the above fields is what gets exported and all subareas that are in A&R are listed in CSV with their associated data
Notes:
report is for viewing purposes
keep in mind that ideally we’d like to share this openly, so creating an api endpoint with different export formats would be useful
Description
This ticket is to enable sysadmin users of A&R to export a report of all parks and subareas within the A& system so they can use it as reference - making A&R source of truth for subarea data and removing the need for us to keep the other excel spreadsheet up to date.
If subareas are added or changed this will happen using BRS-897: Add Park/Subarea POST/PUT functionality and then users can see a full list via this export.
current spreadsheet: https://github.com/bcgov/bcparks-ar-api/blob/main/tools/Park%20Name%20Comparisons.xlsx
CSV export should have the following fields (similar to the existing excel doc). Each row is a sub area.
Acceptance Criteria:
Notes:
keep in mind that ideally we’d like to share this openly, so creating an api endpoint with different export formats would be useful
Linked issues
relates to