DR: Functionality within data register to add new park/protected area

[Dianadec]

Description:

This ticket is to add functionality to the data register for program area to add new sub-areas themselves, without requiring a developer to manually update the register.

• Will need to be split out into design/implementation
• What other considerations might we want to include, given ongoing work with research into sub-areas (https://bcgov.sharepoint.com/:w:/r/teams/031072/Shared%20Documents/%5BProject%5D%20Parks%20Data%20Services/%5BProduct%5D%20Parks%20Data%20Register/4.%20Research/Research%20findings/DR%20sub%20areas%20research%20findings.docx?d=waf8de1b3f20b4153872b97cec07668ff&csf=1&web=1&e=6ck6bx) and dates of operation research

Acceptance Criteria:

Development Checklist:

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

Dependencies

• Blocked by
• 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]

Refinement notes:

• Glenna is the only one with permissions to add this stuff to the system
• We would need to build a front end method for Glenna (or those with equal permissions) to add protected areas to the system.
• Note: there's no api to add parks
• each park and conservancy is defined by an orcs number which we don't have control over generating. challenging because this easily leads to human-error with manual-entry.

[LindsayMacfarlane]

Curious on how many parks need to updated or added per year? What is the current cost of the team doing this vs building out a solution to allow others? Putting as an icebox item/low priority.