You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 14, 2024. It is now read-only.
Do we need lengths on most of the VARCHAR fields? I think PostgreSQL allows varchar fields without lengths. That avoids problems with people with long last names and such.
Do we want enumerated types for radio buttons and similar "select from a fixed list" options? (For instance, gender, race, ethnicity)?
Yes, there are varchar limits on every text field. No action needed.
**Yes, we to replace varchar fields with enumerables when appropriate.
Let's make this a new issue to cover updating: age, gender, race, ethnicity, housing status, family status, income source, income range
Yes we should store phone numbers as only 10 digits and formatting the number on the frontend. Let's make a issue
Veteran is boolean. No action needed
Referral source is using the same db field as clinic name, but the field is poorly named. Instead of 'clinic', it should be 'clinic_name_referral_source'
"Which onsite obligations did the individual complete?" is text for the data entry person. I think it's only a bit of text.
There may be a mismatch between the database's data type and the intake form ui.
Please note any fields that should be changed/removed and the data type you recommend.
The text was updated successfully, but these errors were encountered: