-
Notifications
You must be signed in to change notification settings - Fork 155
3.0 Business Rules
- A Humanitarian Coordinator must be able to view all of the clusters within a disaster.
- A Humanitarian Coordinator must be able to assign a volunteer as a cluster coordinator.
- A Humanitarian Coordinator must be able to send a message to individual or all cluster coordinators.
- A Humanitarian Coordinator must be able to send a message to cluster volunteers.
- A cluster coordinator must be able to view all of the volunteers within their cluster based on a specified date.
- A cluster coordinator must be able to communicate to all volunteers, subsets of volunteers and individual volunteers.
-
A volunteer can commit to volunteer in a disaster for a specific time period.
-
Volunteer profile information:
-
Start date must be specified
-
End date can be left open
-
An (expected) arrival date
-
Email address
-
Cell phone number
-
Disaster
-
Skype ID (future)
-
Notes for anything of a priority nature such as medical issue. open question: Is this relevant?
-
Volunteers will identify by cluster when they register. That is their area of expertise. It's very unlikely that volunteers will change clusters.
-
open question: Can a volunteer commit for multiple disasters/clusters simultaneously? i.e. he is available for several clusters/disaster but later appointed to one of them
-
open question: Is it required to specify the end date? what if the volunteer is available until further notice?
A disaster is identified by a disaster number (DISNO), name, start date and whether it is active.
- the first two digits of the DISNO indicate the fiscal year in which the event occurred;
- the last three digits are sequence numbers within the fiscal year - Numbers 001 through 100 are assigned to declared disasters and numbers 101 through 999 to undeclared disasters. Another mean of identifying disasters is Glide.
- open question Is the disaster name be unique? (this is the current implementation)
- open question What uniquely identifies a disaster? (Is it a DisNo/Glide described above?) [Bill Wagner] Good question, so far we'd like to have a unique 'friendly' name for volunteers'. [moranlf] the friendly name in our system can be unique, but I still suggest that we use some attribute that NGOs are currently familiar with and use it to identify disasters.
- open question The term 'disaster site' was mentioned. is there any relation between a 'site' and a 'disaster' (e.g multiple sites can be opened per disaster), or do they mean the same ?
- Cluster coordinators must be able to send communication to volunteers.
- Volunteers must be able to send communication to cluster coordinators.
- Cluster coordinators must be able to choose one of the following recipient groups:
- on-site volunteers
- remote/off-site volunteers
- all volunteers
- Users must be able to specify the following:
- communication type: email (default) or SMS
- the volunteer active(?) date
- action - choose from a drop list - eg. help, bring equipment
- location - open text field (possibly a drop list?)
- Details - open text field