System Architecture

The following design is no way intended to be a complete design of the database. It is provided to be a reference to the developer.

Global ID Table

Disaster-wide Message ID | Internal ID | Has Response? | CSV of update GIDs

Comments Table

Internal ID | CSV of Comments

Person

Internal ID | pid | Name | Age | Gender | .....

User

Internal ID | pid | Role

Missing Persons Table

Internal ID | pid | source_camp | missing_since | ...

Refugees

Internal ID | pid | ...

Refugee Center

Internal ID | cid | Name | GPS Location | no_refugees | capacity | supplies_available_for

Deceased

Internal ID | pid | time | ....

Supply

Internal ID | cid | Type of resource | Location | Description

Alerts

Internal ID | crid | Type | Location | Refugee Center | Description

Message (compressed)

Map specific tables

The software is expected to have maps functionality built into it, which would have a schema of its own.

Guidelines for DB Sync Daemon

-validate the messages before inserting into the DB (check if the message has all the required fields)

• the records inserted by the user and the ones received from the test server should be validated.