Backcountry: [EPIC] next steps for data collection from first 3 parks

[Dianadec]

Description:

This ticket is to take the inventory, place, permit and policy data collected for our first 3 parks (from camis, bcparks.ca manual review, strapi, and other internal documents) and review it in combination with the geospatial data from citywide (This is a curation ticket.

Note: this is more of an encompassing epic ticket

List of related tickets:

(Captured in # 7 mapping front end setup)--> next steps will include: have ui deployed in aws (minimal map) that is wired up and hooked up to the data that exists in our opensearch right now. therefore deliverable = get it into an environment

NO TENT PADS ARE RESERVABLE for our first 3 parks

• But soon we will want some reservable ones in paradise meadows

Acceptance Criteria:

• [x] data for Cape Scott, Juan de Fuca, and Strathcona is ready to be used for backcountry MVP
• [ ] identify if additional fields are needed in excel data collection template

Development Checklist:

• [ ] ...
• [ ] ...
• [ ] ...

Dependencies

• Blocked by bcgov/reserve-rec-api#36
• Blocking

Relevant documentation as reference

Definition of Ready

• [ ] Acceptance criteria are included
• [ ] Wireframes are included (if applicable)
• [ ] Design / Solution is accepted by Product Owner (if applicable)
• [ ] Dependencies are identified (technical, business, regulatory/policy)
• [ ] Story has been estimated (under 13 pts)

Definition of Done

• In progress:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] UI meets accessibility requirements
  • [ ] Unit tests are written
  • [ ] Work is traceable in GitHub
  • [ ] PR linked to ticket number
  • [ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment
• Code review:
  • [ ] Code is peer reviewed and has passed CI/CD tests
• QA:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] Code is potentially shippable to the production environment
  • [ ] Functional features have been tested and passed by QA
  • [ ] UI components tested by designer
  • [ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
• PO Review:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] Reviewed and approved by Product Owner

Notes:

[Dianadec]

the work that comes after this: https://github.com/bcgov/reserve-rec-api/issues/15 Darcie to refine

[meyerdarcie]

@cameronpettit as discussed, unblocking this ticket. Data collection spreadsheet for first three parks is available here: https://bcgov.sharepoint.com/:x:/r/teams/08548/Shared%20Documents/General/1.%20Project%20Documentation/4.%20Parks%20%26%20Rec%20Digital%20Transformation%20Project/DATA%20FOLDER/Data%20Collection%20Backcountry%20-%20Cape%20Scott-JDF-Strathcona.xlsx?d=w97e683ba1c344f8c8c3aabfcf23c569d&csf=1&web=1&e=vxNNVY

[Dianadec]

@cameronpettit will create a ticket covering what he's working on as a task broken out from this epic. Pulling this epic out of the sprint. cc @LindsayMacfarlane