Requests and Open311
When a requester uses an Open311 compliant application to submit an issue to Cartegraph there are some specifications:
- If the Open311 request sends information in a field not listed in Cartegraph, that information is not saved to the request in Cartegraph.
- If the Requester cannot be created, it changes to anonymous and is logged in the Error Log. For example, if Cartegraph‘s Birthday field is required, but the application used to submit the request does not have a Birthday field, the Requester cannot be created and the request is submitted as Anonymous.
- An existing Requester is selected if the First Name, Last Name, and Email Address match.
- If the Open311 Requester contains a First Name, Last Name, and Email Address, but does not match an existing Requester in Cartegraph, a new Requester record is added to the Requester library and used in the Requester Log for that request.
- The Request Issue’s Code field is required for Open311 compatibility. Open311 requires a code to create the request.
Open311 Field to Cartegraph Field Mapping
Open311 Field |
Cartegraph Field |
---|---|
Service_Request_ID |
Requests\ID |
Status |
Requests\Status |
Status_Notes |
Requests\Response Notes |
Service_Name |
Requests\Issue\Issue |
Service_Code |
Requests\Issue\Code |
Description |
Requests\Description |
Agency_Responsible |
Requests\Agency Responsible |
Service_Notice |
Requests\Issue\Response |
Requested_DateTime |
Requests\Entry Date |
Updated_DateTime |
Calculated (Last Modified, or Close Date if Status = Closed.) |
Expected_DateTime |
Requests\Due Date |
Address |
Requests\Location Description |
Address_ID |
Requests\Address ID |
ZipCode |
Requests\Zip Code |
Lat |
Calculated (Request Spatial) |
Long |
Calculated (Request Spatial) |
Media_URL |
Calculated (All Open311 Attachments) |