UI Design - correct information on the register

[RFK250]

User Story

As a MH staff user, I need to be able to make corrections to the registry on behalf of the public so that I can ensure the integrity of the registry.

Pending Requirements

---

Notes

• Re-use existing code and components for data validations and lookups where possible (or where necessary for DB2 architecture), new ones can be added in future increments
• Re-use existing visual design elements where possible, otherwise only create minimally viable visual elements (again, can be updated in future increment)
• "Correct Registration Details" options will only be visible to MH Staff users at this time
• Ignore the "Other" field from the application (see image below) - more user research into this field needed, to be done in future increment

---

Images

From the form - these are the fields that can be corrected by staff on behalf of the user - red lines indicate groupings of elements

[mstanton1]

@tlebedovich were you involved in any discussions with Kyle when he was PO on correcting information on the register? My thought is this might have been an outline he created without requirements/ design. If so, I'll close/repurpose these so we have our own UI Design ticket to start and can create dev tickets off that as per current process.

[tlebedovich]

I was not in any discussion about this so not sure if its still accurate. I would assume the correction form would be the place to start for requirements gathering though. What I don't see on the form is giving Staff the ability to correct the name and contact information of the owners, interest etc. ie in case of a typo made

[mstanton1]

Correction and amendment are covered under #18555.