Open arlentees opened 3 months ago
Notes from call: Most text fields are UTF-8 which supports by default the character sets Place names seem to save ok PDF seems to save ok Searches will accept and display characters in the web UI, need to test further with results Validation on Personal Names seems to fail - API is limiting for business/personal names for Owners, (submitting party?, same for PPR) - based on a constraint set by Corp. Registries and DB2 for Business Names rules.
Does not save back into legacy DB2 correctly (character replacement)
Question regarding whether or not screenreaders would be able to pronounce the name correctly
Few external client for MHR API - BC Assessments and possibly one other ministry to search via API
A long term goal of registries is to be able to enable the correct use of Indigenous Language names across the suite of products. The MHR and PPR would be providing value to users who whish to use indigenous names in these systems, and the work aligns with Chapter 12 Core Policy Digital Principles to Express cultural and historical awareness and respect
Readiness Work