Closed warlokkz closed 8 years ago
string
string
array
string
string
string
string
uuid
array
(list of district ids)date
uuid
number
bool
bool
bool
bool
bool
bool
bool
date
string
string
number
date
bool
string
number
number
string
string
geo?
string
date
string
string
number
bool
bool
string
string
bool
string(encrypt)
string
number
bool
uuid
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
number
string
string
string
string
array
date
number
string
(encrypt)bool
string
number
number
number
number
number
number
number
number
number
number
bool
bool
bool
bool
bool
bool
bool
bool
bool
bool
bool
bool
bool
bool
bool
bool
bool
bool
bool
bool
bool
bool
bool
This is a crucial part of the app, and needs some time to think about design of the schema. Ideally, we want something that can be modified by whomever decides to adopt the project after this. We should come up with a minimum requirements list for what we will be collecting from the form.
Ideally, I would like to have a time-series or versioning capable database, so that if the administrators decide to change the schema (form questions), we can adjust for that on the server side. What other collections/tables could we have besides form data?
Suggestions:
Users (for logging in and giving permissions) ? Locations (could be sorted by districts, addresses or geolocation - depending on the granularity we want) Persons (the homeless whom are being assessed) Assessments (attached to Persons) \ I think keeping different versions of assessments that are attached to Persons can be good for keeping a time-series or versioned system to easily query for progress / tracking. Using this schema can most definitely fit a RDBMS like PostgresQL or a graphDB like ArangoDB.