Service Request Fields

[Zvi Band]

Can we get an explanation of each of these fields?

{"serviceorderdate"=>"2001-03-28 20:05:00", "resolution"=>0,
"servicerequestid"=>123456, "serviceorderstatus"=>"S0596",
"servicenotes"=>26, "servicetypecodedescription"=>"ABANDONED AUTO",
"servicetypeocode"=>"AA", "servicecodedescription"=>"ABANDONED
VEHICLES (PUBLIC)", "servicecode"=>"S0001", "servicepriority"=>nil,
"aid"=>"244012", "serviceduedate"=>"2001-03-29 08:39:00",
"resolutiondate"=>"2001-03-08 15:17:00", "agencyabbreviation"=>"DPW"}

[Dmitry Kachaev]

Here is a metadata file on 311/Hanses. See fields description at the bottom of the page.

http://data.octo.dc.gov/Metadata.aspx?id=4

-Dmitry

Dmitry Kachaev
cell    - (703) 477-6072
email - dmitry....@gmail.com

[Zvi Band]

Thanks Dmitry,
However, it looks like a lot of the fields that we'd like out of the Service Request, and is listed on that page, is not present or incorrect in the API Call

Examples:

• SERVICEORDERSTATUS  - Is "S0596" in the API call, but supposedly should be:
  • Open /
  • Closed /
  • Open overdue /
  • Closed overdue /
• SERVICEPRIORITY - nil?
• RESOLUTION - dont see this here
  

--
---
Zvi Band
http://zviband.com
202-683-7803
ASAP? https://awayfind.com/zvi

[Dmitry Kachaev]

This is fixed.

Here is new output sample:

{{"servicerequest": 

[{"servicerequestid": 2116063}, 

{"servicepriority": "NO VALUE ASSIGNED"}, 

{"servicecode": "S0278"}, 

{"servicecodedescription": "PARKING METER - NO TIME FOR COIN"}, {"servicetypeocode": "METERS"}, 

{"servicetypecodedescription": "PARKING METERS"}, 

{"serviceorderdate": "2009-05-06 06:35:00"}, 

{"serviceorderstatus": "CLOSED"}, 

{"agencyabbreviation": "DDOT"}, 

{"resolution": "METER FOUND WORKING"}, 

{"resolutiondate": "2009-05-08 05:15:00"}, 

{"serviceduedate": "2009-05-12 06:35:00"}, 

{"servicenotes": "Close Ticket. "}, 

{"aid": "244012"}]}

Dmitry Kachaev
cell    - (703) 477-6072
email - dmitry....@gmail.com