ParkID Generator (UI)

As a BC Parks planner and/or registrar I need use a unique identifier for parks so that we can easily track parks across systems, tools, and time.

This ticket is to implement the ParkID (formerly ORCS) generator so that these unique identifiers are autogenerated and associated with a park name.

Acceptance Criteria:

• UI matches designs and specs in Figma, linked below (UI numbers 2.0 – 2.4)

2.0 ID generator
2.1 Generate ID - choose type
2.1.1 Select associated protected area
2.1.2 Add temporary name
2.3 Edit temporary name
2.4 Cancel ID

• ID generator can be accessed from the home page

• ID generator can be accessed from the left nav

• User can view and search pending and cancelled IDs

• User can generate a new ID for a protected area

• User can generate a new ID for a site or unofficial site (depends if these are going to be differentiated by ID format)

• User can select which protected area the site or unofficial site is a part of

• User can add a temporary name connected to the ID

• User can edit temporary name - these changes will not be tracked as 'historical changes'

• User can save any changes made

• User can find new ID record in the pending IDs table

• User can find new record by searching for the temporary name or ID

• System will give the ID the status of 'pending'

• User can cancel an ID

• System will change the ID status to 'cancelled'

Notes:

• Relates to #85 and #56 and #29

Requirements notes

Protected area requirements

• user must select a park type (protected area, site, or unofficial site)
• user must add a park name
• park name can be edited while pending and changes are not tracked historically
• if user cancels when editing a park name they will return to Park ID home page
• default view of table on park ID home page shows no results
• user can search by park ID or Name

Site or unofficial site requirements

• click link to create new ID
• user must select a park type (protected area, site, or unofficial site)
• user must associate a protected area prior to generating a park ID
• user must add a park name
• park name can be edited while pending and changes are not tracked historically
• if user cancels when editing a park name they will return to Park ID home page

Review the linked Figma flows for UI 2.0–2.4 and related issues #85, #56, and #29 first. Then trace the home page and left-navigation entry points described in the acceptance criteria. Done means the generator supports pending and cancelled IDs, protected-area associations, temporary names, searching, saving, and cancellation across the specified flows.