aarontitus
commented
11 years ago From v...@aarontitus.net on April 13, 2013 01:50:19 • name: String. E.g. “zip_code” • phase: Enum string. Name of the phase to which this task belongs. A task may have one phase. The phase is used to build customized maps and build the Claim, Status and Report section, which must include at least a “Claim for” and “Current Status” for each unique phase named in the form.
- Enums should also contain a enumerating the acceptable values: E.g. “cleanup”, “rebuilding”, “mold_remediation”, etc. • is_required: Boolean. Although not used right now, eventually it will be used to automatically generate javascript validation. We should get in the habit of adding these now so that when we create the automatic javascript validation, it will apply retroactively. • class: String. HTML “class” • type: String. HTML “type” • checked: String. HTML “checked” only if a Boolean. • default_case: Enum: “TRUE”, “FALSE”, “NULL”, “NONNULL”. Most defaults will be NULL or FALSE (e.g. “Carpet Removal,” or “drywall removal”). However, occasionally the default case will be TRUE (e.g. for “Home is habitable,” the default is TRUE. Unchecking the box will create the non_default_case which is worth reporting.) • english_equivalent_non_default_case: an English equivalent statement for the non-default case, (e.g. “Home is not habitable”, “Downed Wires”). “NULL” means that there is no English equivalent statement. Only non-default cases will appear in the InfoBox and Printer Friendly version. • display_in_infobox: Boolean. If TRUE, then the English equivalent of the non-default case of this attribute will appear in the Infobox and Printer Friendly version.
Original author: v...@aarontitus.net (January 13, 2013 22:21:04)
For each new Incident, the administrator will create an Incident-specific Assessment/ Intake form by picking from among these data points. For example, if there is an earthquake in California, the administrator will include only earthquake-related issues, but not flood-related issues on the assessment/intake form (unless there was an associated tsunami, for example).
Each incident Assessment Form should be automatically saved, and may be used as a template starting point for future Incident Assessment Forms.
This issue relies upon the creation of a Data Point bank described in #135. Each organization may have a unique view of this form, depending on the types of work they do (See #137).
Original issue: http://code.google.com/p/sandy-disaster-recovery/issues/detail?id=136