Which functionalities the data should have (not the data architecture, for the moment...)
Some part of the EmerMan will have public access also in write operation (i.e. create a new emergency). For this reason, it should be possible to be able to trace some or all the user operations to:
Part of the data should be able to migrate / replicate / forward / synchronize between one or more offline devices or removable parts (point = offline device or removable part).
Migrate: the data from point A is transferred to point B
Replicate: the same data is shared between two points and/or the main core.
Forward: the data from point A is transferred to point B through point C.
Synchronization: changed made in different points and/or in the main core, concerning the same item or different items, should be synchronised to reach a common final state.
The main use should be the offline mode: when there is no Internet connection, the devices should be able to collect, share, transport information so when a device reaches Internet the main core can be updated with as much information as possible.
The data should be mergable and splitable. It should be possible, i.e., to take two different emergency situations and to merge them into a new one or to take an area and to split it in subarea moving existing data to the right subarea. (Area and subareas will be explained later...)
The data should be easily imported and exported from/to external entities.
This is important to be able to use EmerMan also inside already existing environments without asking to use only EmerMan.
The import/export operation should be manually or automatically invocated.