It is vital for organizations to understand which areas have been canvassed, to
properly deploy assistance. Occasionally there will be a city block where one
apartment complex is canvassed dozens of times, while the next door apartment
complex is completely ignored.
A canvassing record is different from and less formal than a Work Order record,
although a canvassing record labeled "Assessed" is automatically created for
each completed assessment. The primary purposes of a Canvassing Record are: 1.
to identify the areas that have been canvassed. 2. Help identify areas that
need additional action because they need follow-up, or because the data is old.
Duplicate canvassing records are permissible and inevitable. No attempt to
identify duplicate canvassing records is necessary as long as the timestamp is
accurate. Basically, canvassing records should become stale with time.
A Canvassing Record should include:
* Status (Required). Valid Statuses (or their aliases):
* No Needs: No Help Wanted
* No Needs: Unaffected
* No Needs: Helped by Others
* No Needs: Rejected (Please Explain)
* No Needs: Needs are Out of Scope
* Follow Up: Nobody Home
* Follow Up: Owner Not Present
* Follow Up: May Need Help in the Future
* Follow Up: Needs Help, but Not Ready
* Needs Help/ Assessed [If this selection is chosen in the interface, then the user is forwarded directly to the Assessment/ Intake form, before creating a Canvassing Record. After the assessment is complete, a Work Order record is created, and also Canvassing Record at the same time]
* Status Notes (Optional). A text field with additional explanation of the
status, if desired.
* Name (Optional). A text field
* Phone Number (Optional)
* Address (Required). If the lat/long is provided by the mobile device, then
the Google API should guess all of the Address fields. Note: For the mobile
device interface, the street number should be placed in a separate field for
easy manual correction, as that is the most likely portion of the address to be
incorrect.
* Lat/Long (Required). The Lat/Long should be requested from the (mobile)
device first. If the mobile device gives a Lat/Long, then the address is
guessed. If the mobile device does not give a lat/long, then an address is
manually required, and the Google API fills in the Lat/Long.
* Work Order ID (Optional). If status is "Assessed", then there should be a
link between the Canvassing Record ID and the Work Order ID. This will allow
the system to create a link to the Work Order from the Canvassing Record
interface(s). This field is automatically generated if and only if a work
order is created.
See related issues regarding canvassing maps.
Original issue reported on code.google.com by v...@aarontitus.net on 1 Jan 2013 at 10:13
Original issue reported on code.google.com by
v...@aarontitus.neton 1 Jan 2013 at 10:13