Backcountry -> Data for first three parks

[Dianadec]

Description:

As a more focused version of ticket #9 , this one is to specifically look at data for Cape Scott, Strathcona, and Juan de Fuca.

• reconcile what's missing for them
• complete data model for those

Acceptance Criteria:

• [x] Attach spreadsheet with data collected to data from first 3 parks : https://bcgov.sharepoint.com/:x:/r/teams/08548/_layouts/15/Doc.aspx?sourcedoc=%7B97E683BA-1C34-4F8C-8C3A-ABFCF23C569D%7D&file=Data%20Collection%20Backcountry%20-%20Cape%20Scott-JDF-Strathcona.xlsx&action=default&mobileredirect=true
• [ ] According to criteria in #6, program area to compile available data for:
  • [ ] Cape Scott
  • [ ] Strathcona
  • [ ] Juan de Fuca
• [ ] Review data alongside workflow diagram

Development Checklist:

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

Dependencies

• Blocked by
• Blocking

Relevant documentation as reference

• DATA FOLDER ---> Where relevant data docs/links are saved 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]

Notes from July 16 mtg: What experiences do we want to host in our reservation system? What is the exhaustive list of opps we want to offer in this backcountry reservation system? Answers we heard:

• just copy what's in camis or just what bcparks.ca offers So if that's it, then we need someone to go in and list it in a much more consumable format. ISSUE = it's not in a consumable format. So someone needs to go through bcparks.ca and camis to get the data and information.

Inventory Permits Policies Operating Schedules Places

In the 3 parks, which experiences are we doing? Who decides this?

Idea: Exercise: what's in citywide (raw data) and what's in camis? and merging the disconnect

The 3 Backcountry experiences we need to decide on: cape scott strathcona juan de fuca

[ndelraye]

this is the bits I found when I took a quick look - https://bcgov.sharepoint.com/:w:/r/teams/08548/Shared%20Documents/General/1.%20Project%20Documentation/4.%20Parks%20%26%20Rec%20Digital%20Transformation%20Project/Backcountry/cape%20scott.docx?d=w7eb588480ac9464b9e3c6ec6171ef6e9&csf=1&web=1&e=1p6vqF