76 | | === 3 x Create disaster scenarios & demos with data through pre-populate === |
77 | | |
| 76 | === Create disaster scenarios & demos with data through pre-populate === |
| 77 | |
| 78 | The objective is to collect real or at least realistic data which can be used to illustrate some of the capabilities of Sahana Eden. The task requires a little research on the disaster risk reduction, preparedness and response capabilities in your location. |
| 79 | |
| 80 | You will need to collect some data and save them in a format that can be imported directly into Sahana Eden. This will be achieved by creating a number of CVS files and conforming strictly to the format described in each file. |
| 81 | |
| 82 | Note: When adding personal information it is essential that the data have been modified such that it can not be used to identify any real person. As a general rule all email addresses should be from the example.com domain, thus the email address for Joe Bloggs might be joe.bloggs@example.com, phone numbers should look realistic but should not be true numbers. |
| 83 | |
| 84 | Within Eden all email addresses must be unique, so as to avoid any clash with existing data or data generated by other participants include your melagne id immediately before the @, thus for an id of 2154, joe blogg's email would become joe.bloggs2154@example.com. |
| 85 | |
| 86 | To complete the task you will need to meet the following minimum specifications: |
| 87 | |
| 88 | Each scenario must contain a brief description. This must be no more that 500 words (approximately 1 page of text) describing the following: |
| 89 | * The setting, location (country province) |
| 90 | * The type of disaster the organistions are preparing for |
| 91 | * Any known problems with existing disaster response capabilities |
| 92 | |
| 93 | Easy |
| 94 | ||=Type of resource =||= Number of entries =||= File =|| |
| 95 | || Organisation || 3||org/organisation.csv || |
| 96 | || Office || 6|| org/office.csv || |
| 97 | || Warehouse || 3|| org/office.csv || |
| 98 | || Staff || 50|| hrm/person.csv || |
| 99 | The recommended means of testing for this task is, to successfully open as a spreadsheet file, but saved as a CSV file, however if the student is able to set it up in a pre-populate folder that will make up for any significant shortfall in the entries. |
| 100 | |
| 101 | Medium |
| 102 | ||= Type of resource =||= Number of entries =||= File =|| |
| 103 | || Organisation || 4|| org/organisation.csv || |
| 104 | || Office || 8|| org/office.csv || |
| 105 | || Warehouse || 6|| org/office.csv || |
| 106 | || Staff || 70|| hrm/person.csv || |
| 107 | || Staff skills || 200|| hrm/skills.csv || |
| 108 | || Assets || 30|| asset/asset.csv || |
| 109 | || Stock || 120|| inv/inv_item.csv || |
| 110 | The recommended means of testing for this task is, attempt to import the data into eden using the menus. However if the student is encouraged to try and set it up in a pre-populate folder. |
| 111 | |
| 112 | Hard |
| 113 | ||= Type of resource =||= Number of entries =||= File =|| |
| 114 | || Organisation || 5|| org/organisation.csv || |
| 115 | || Office || 10|| org/office.csv || |
| 116 | || Warehouse || 8|| org/office.csv || |
| 117 | || Staff || 100|| hrm/person.csv || |
| 118 | || Staff skills || 200|| hrm/skills.csv || |
| 119 | || Assets || 40|| asset/asset.csv || |
| 120 | || Stock || 120|| inv/inv_item.csv || |
| 121 | || Request for stock items || 120|| req/req.csv || |
| 122 | |
| 123 | The recommended means of testing for this task is, attempt to import the data in a pre-populate folder. The data must be delivered in a single folder suitable for pre-populate even if the student was unable to run the pre-populate task. |