jim-mcgowan
commented
3 years ago Incident CSV export fields:
- date
- incident_number
- incident_type
- incident_call_type
- cas_event_number
- status
- address
- city
- state
- zip
- county
- lat
- lng
- narrative
- units_destroyed
- units_major
- units_minor
- units_affected
- num_people_injured
- num_people_hospitalized
- num_people_deceased
- num_adults
- num_children
- num_families
- assistance_given
- incident_verified
- dispatch_relayed
- responders_identified
- dat_on_scene
- dat_departed_scene
- responder_name_1
- responder_role_1
- responder_flex_1
- responder_name_2
- responder_role_2
- responder_flex_2
- responder_name_3
- responder_role_3
- responder_flex_3
- responder_name_4
- responder_role_4
- responder_flex_4
- responder_name_5
- responder_role_5
- responder_flex_5
- responder_name_6
- responder_role_6
- responder_flex_6
- responder_name_7
- responder_role_7
- responder_flex_7
- responder_name_8
- responder_role_8
- responder_flex_8
- responder_name_9
- responder_role_9
- responder_flex_9
- responder_name_10
- responder_role_10
- responder_flex_10
frankduncan
Right now administrators use Sisense Periscope to generate various reports (via direct SQL queries that therefore need to be maintained on the Periscope side). This mean DCSOps effectively has a dependency on that third-party service. These reports are not very complex and could easily be generated by DCSOps directly.
This is related to issue #257, in the sense that this too is about publishing data out of DCSOps in both parseable and human-readable form. Ideally we would do both enhancements at once, since much of the same code is likely to be touched.