PRDT: Minimum viable dataset

[meyerdarcie]

Description:

[Need to chunk out this ticket per park at a time]

This ticket is determine requirements and criteria for our minimum viable dataset for a backcountry prototype, as referenced in #6

Acceptance Criteria:

• [ ] Template for data for backcountry parks is complete (inventory, permits, places, policies)
• [ ] Data spreadsheet has been reviewed/validated by program area (someone needs to go through the fields and determine what they actually mean).

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]

Qs for refinement: What are the gaps, how will we find/determine that? What is this ticket about

[Dianadec]

Todo: get more information re: Strapi and work with Rob Some info in this teams thread: https://teams.microsoft.com/l/message/19:24137c6e9eba4bb7b32a82fe6dd469b9@thread.tacv2/1719956073977?tenantId=6fdb5200-3d0d-4a8a-b036-d3685e359adc&groupId=cb2c4bec-527d-4097-80b2-6e40e98d36bf&parentMessageId=1719956073977&teamName=Parks%20%26%20Recreation%20Transformation%20(Open%20X-Gov)&channelName=%5BTeam%5D%20PRDT%20Internal%20Collab%20(Closed)&createdTime=1719956073977&ngc=true

[Dianadec]

Also need: one Source of truth for dates - Amanda from oxd has a mural board. For park names, the data register will be the source of truth

another todo: generate list of current dataset info and get feedback on it

[Dianadec]

DR sub areas research findings: https://bcgov.sharepoint.com/:w:/r/teams/031072/_layouts/15/Doc.aspx?sourcedoc=%7BAF8DE1B3-F20B-4153-872B-97CEC07668FF%7D&file=DR%20sub%20areas%20research%20findings.docx&wdOrigin=TEAMS-MAGLEV.p2p_ns.rwc&action=default&mobileredirect=true

[Dianadec]

@cameronpettit Darcie's question for ya: What data are we missing for backcountry mvp and how might we find it? cc @meyerdarcie

[Dianadec]

Refinement notes:

• we do have the raw data of the initial several parks
• but geospatial isn't in the right spot, but they are pretty good
• In the current format, assume it's perfect

[Dianadec]

Going to create a new ticket that is a more focused version of this one.

[meredithom]

Refinement notes:

• To explore further: How data updates are going to happen and how that will be communicated to regional staff

• We should be keeping track of data sources as we go in the spreadsheet

• DR will be our source of truth for protected area and subarea names

• DB keeps track of last updated dates of data and surface in admin side of application

• Start with parks that have the most complete data (best data will be from parks with inventory)

Todo:

• diagram of our process around gathering data