911-Adjacent dataset exploration

[doub1ejack]

Overview

Create a list of specific datasets that would expand the usefulness of the 911 call data. Perform a simplified cost/benefit analysis for each dataset by describing the potential value-add, the availability of the data, & the feasibility/effort of associating data with open 911 call for service data.

Goals

1. Identify 911-adjacent datasets: Create a list of datasets and sources that have some relation to 911 Call-for-Service data. Describe the benefits and insights that would become newly available with this data.

2. Cursory evaluation of each dataset: Where possible, try to explain or speculate on a. How this data could be connected to the 911 data (shared ids, etc), b. Whether access to this data is public or limited (FBI clearance, academic researchers, etc), c. How widely available this data would be (could it be connected to most of the 6k PSAPs, or just a limited subset?)

3. Samples (when handy): If a sample of the dataset or the schema will be included, but only if they are readily available. (See Possible Next Steps below.)

Outputs

• A written document containing
  • a paragraph bio/summary of the people doing this research
  • executive summary
  • recommendation of datasets that would help surface calls that don’t require a law-enforcement response (key R911 goal)
  • recommendation of up to 3 of the most accessible datasets
  • recommendation of up to 3 of the most aspirational datasets
  • a list of individual datasets/sources that includes information outlined in the "Goals" above

Possible Next Steps

If some datasets are found to be particularly appealing, what might be some of the next steps?

• Software discussion: discuss technical considerations of how additional datasets might be incorporated.
• Data exploration: a deeper dive could be conducted by a small team of members to find samples and understand access and availability.

Action Type

Some general norms & information for this type of Reimagine911 action:

• Ad-hoc
  • This action will have a testing period of ~2 weeks, after which we'll consider retiring the work or making it a R911 activity
  • Any member may comment & discuss action, but action assignees are not obligated to respond
  • People are assigned to this action by program managers and action leaders.
• Exploratory
  • This action will inform future decisions based on it's findings.
  • A summary will be written up when the initial exploration is complete.
• Individual
  • The initial phase of this work (~2 weeks for an exploratory project) will be primarily done by a single individual
  • The primary assignee has the discretion to pull in helpers as they see fit.

Communication

• Slack channel: none
• Google drive folder: none
• Notion orientation docs: none

Documents & Resources

Notes from Micah & Jerry's initial meeting.

[jerryhall]

Ok, I'm finally free for a bit so will be working on this over the next week.