Call-for-Code-for-Racial-Justice / Call-for-Code-for-Racial-Justice/Open-Sentencing
Epic - Data gathering (Collect More Data/Track)
- Dominant language
- No language data
- Stars
- 76
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
We need to clearly understand the risks/considerations involved in adding more data to our solution. We'll then determine any follow-ups.
**Data Gathering:** We'd love your help!
[Data.Source.Inventory.Open.Sentencing (1).xlsx](https://github.com/Call-for-Code-for-Racial-Justice/Open-Sentencing/files/7324000/Data.Source.Inventory.Open.Sentencing.1.xlsx)
**Please go ahead and edit**
**Anyone of any skill level can help!**
Start with brainstorming a list. We can work as a team to take action. Consider a clear tracking spreadsheet or other method to ensure we've identified and cleared all risks.
In researching data, make edits to the Excel sheet. Think about the following to track.
- Ensure data is free of cost
- Ensure legally we are not hitting any issues in using our data. Is IBM legal still available to help as we add data sources?
- Ensure any licensing rules are followed.
- For this data, it may not be available. Sentencing data can be at various levels (city, state, county, Federal). We have to have a way to account for gaps as more is accumulated.
- We need a way to start with what we can find, and build from there. (Ex start with Cook County, Federal, then gather more)
- Data management - Do we have a method to store/manage/and maintain quality coming in from various sources?
- Ensure unexpected bias is not present in the data.
- Ensure data coming in has enough info/quality for it to be useable. Do we need a data governance process to ensure we trust the data and new data as it comes in?
- Ensure data is handled in a secure manner.
- Determine the most automated ways to update data as refreshes are available.
- Can we avoid malicious users from editing our data?
Contributor guide
Assessment
This issue has not been assessed yet.