|
Next revision
|
Previous revision
|
req:ics_reporting_form_214 [2009/11/17 05:52]
mprutsalis created |
req:ics_reporting_form_214 [2010/12/18 17:35] (current)
|
| - Operational Period: This is a date & time - beginning and end - to be defined by a pop-up box when the user selects the generate ICS 214 report button - and will also define the range of a time period that further queries will take place. | - Operational Period: This is a date & time - beginning and end - to be defined by a pop-up box when the user selects the generate ICS 214 report button - and will also define the range of a time period that further queries will take place. |
| - Personnel Roster Assigned: These three fields will be pulled from queries based on volunteers assigned to the project specified in field 4 for the operational time period specified in field 6, as follows: Name = Name of volunteer; ICS Position = position assigned in project; Home Base = location set upon registering in the VMS as home location. | - Personnel Roster Assigned: These three fields will be pulled from queries based on volunteers assigned to the project specified in field 4 for the operational time period specified in field 6, as follows: Name = Name of volunteer; ICS Position = position assigned in project; Home Base = location set upon registering in the VMS as home location. |
| - Activity Log: These two fields are pulled from a general query of any data element within the active and utilized Sahana libraries - including the organization registry, the shelter registry, the request management system, the inventory system, the missing persons or disaster victims registry, or a manually entered situation in the situation awareness module, that are entered by a Sahana registered user associated with the selected "project" - i.e. the "site manager" position or any other assigned volunteer - and within the operational period. All such data elements would be listed and sorted by time (earliest first) and summarized as to what the entry or change in Sahana data was. | - Activity Log: PHASE 1: Leave as blank fields to be manually entered by the user. We have been advised that the unit leader is usually going to want to come up with own summary of the major events from the reporting period. PHASE 2 (possible future enhancement or demonstration of capabilities - DO NOT CODE THIS NOW): These two fields are pulled from a general query of any data element within the active and utilized Sahana libraries - including the organization registry, the shelter registry, the request management system, the inventory system, the missing persons or disaster victims registry, or a manually entered situation in the situation awareness module, that are entered by a Sahana registered user associated with the selected "project" - i.e. the "site manager" position or any other assigned volunteer - and within the operational period. All such data elements would be listed and sorted by time (earliest first) and summarized as to what the entry or change in Sahana data was. |
| - Prepared by (Name and Position): This would be pulled from the user logged into Sahana (the name) and position would come from the position assigned to that individual from the VMS. \\ | - Prepared by (Name and Position): This would be pulled from the user logged into Sahana (the name) and position would come from the position assigned to that individual from the VMS. This should almost always be the same as the unit leader name and position from field 5 above.\\ |
| \\ | \\ |
| **Additional Requirements & Notes**: It would be good to have the following functionality as well - though this is not required for the proof of concept: | **Additional Requirements & Notes**: It would be good to have the following functionality as well - though this is not required for the proof of concept: |
| * The ability to manually edit the report before it is exported/finalized i.e. you see all auto-generated data on an editable screen/form which allows the user to manually edit any/all data elements before finalizing and submitting the form for printing/export/conversion to PDF or word document. | * The ability to manually edit the report before it is exported/finalized i.e. you see all auto-generated data on an editable screen/form which allows the user to manually edit any/all data elements before finalizing and submitting the form for printing/export/conversion to PDF or word document. This would also be used for the user to enter the event information in field 8. |
| * The printed/exported form needs to look as much as possible like the sample template form provided in the link above. This includes all labels, shading, fonts, and form numbers in the footer. \\ | * The printed/exported form needs to look as much as possible like the sample template form provided in the link above. This includes all labels, shading, fonts, and form numbers in the footer. \\ |
| \\ | \\ |
