[M] A&R Research: notes field for A&R

[JLWade]

Description:

We need way to record changes to sub-areas/method of collection etc. for each park that affect long term interpretation of data. This ticket is to research how a notes field at the park level in could support long term interpretation and management of A&R data.

Acceptance Criteria:

• [ ] determine how we can incorporate a notes field into the A&R tool
• [ ] write any implementation tickets for prioritization of this work and add to backlog

Development Checklist:

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

Dependencies

• Blocked by
• Blocking

Wireframe(s):

Workflows:

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

• [ ] User story is included
• [ ] User role and type are identified
• [ ] Acceptance criteria are included
• [ ] Wireframes are included
• [ ] Design / Solution is accepted by Product Owner
• [ 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:

[nicolebottoms]

Wanted to add some more context to this. This would be used at the park level, where we could add notes for changes to park reporting or spatial changes that impact reporting. An example of this would be Shuswap Marine; prior to 2022 camping data was reported under Cinnemousun Narrows Park, which is technically within Shuswap Marine Park, but the camping where it is recorded has changed. Or Garibaldi has a few more sub areas added recently, but those sub areas also include areas of the park that aren't explicitly noted in the sub-area ie. Cheakamus sub-area not only includes Cheakamus Lake, but also Helm Creek campground and Singing Creek Campground.