Closed timbot1789 closed 1 month ago
This ticket was partially completed in this PR: https://github.com/codeforpdx/PASS/pull/515
It implemented the data model, and added part of the UI. What remains is UI implementations for the following fields:
These 3 are all enums, and should be represented as <select> element or an MUI equivalent.
The options for the select element are in the description. The values on the left of the colon MUST be the values stored in the profile. The values on the right are the labels to show to the user. You may change these if you think of a better wording.
Filed PR on this, #633 - 513 enhancement civic profile housing information form.
Issues should not be closed until the related PR has been fully merged.
Describe the Current Behavior/Feature:
We are currently building out a Civic profile to use with civic services.
Proposed Behavior/Feature:
Part of this profile should contain information on a person's housing situation. Where did they live last? How secure is their housing, etc?
Proposed Implementation (if applicable):
Add the following fields to the
civic_profile.ttl
data store and add a UI to the Civic Profile page to edit them:urn:hud:hmis:owl#LastPermanentCity
: The city component of their last permanent addressurn:hud:hmis:owl#LastPermanentState
: The state component of their last permanent addressurn:hud:hmis:owl#LastPermanentStreet
: The street component of their last permanent addressurn:hud:hmis:owl#LastPermanentZIP
: The ZIP code of their last permanent addressurn:hud:hmis:owl#MonthsHomelessPast3Years
: An enum describing how long they've been homeless in the past 3 yearsurn:hud:hmis:owl#TimesHomelessPast3Years
: An enum describing how many times they have lost their housing in the past 3 yearsurn:hud:hmis:owl#TimeToHousingLoss
: Enum describing how long until they will become homelessAdditional context:
It may be worthwhile to to map or prepopulate some of these values (e.g. address) from similar values found in other public profiles in a client's pod.