Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Epic - Data gathering (Collect More Data/Track) #31

Open
sforsyth089 opened this issue Sep 16, 2021 · 6 comments
Open

Epic - Data gathering (Collect More Data/Track) #31

sforsyth089 opened this issue Sep 16, 2021 · 6 comments

Comments

@sforsyth089
Copy link
Collaborator

sforsyth089 commented Sep 16, 2021

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

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?
@sforsyth089
Copy link
Collaborator Author

sforsyth089 commented Sep 17, 2021

I can draft a check list of our requirements by source. (with preferences and some history of the data)

@sforsyth089 sforsyth089 changed the title Identify risks/considerations associated with data gathering Data gathering (Collect More Data/Track) Oct 1, 2021
@sforsyth089 sforsyth089 added hacktoberfest help wanted Extra attention is needed labels Oct 1, 2021
@sforsyth089
Copy link
Collaborator Author

Updated data sources under investigation.

@joannhh
Copy link
Collaborator

joannhh commented Oct 11, 2021

Added a da
Copy.of.Data.Source.Inventory.Open.Sentencing.1 (1).xlsx
ta source being investigated.

@github-actions
Copy link

👋 Hi! This issue has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed.

@github-actions github-actions bot added the stale label Nov 22, 2021
@upkarlidder upkarlidder removed the stale label Jan 28, 2022
@upkarlidder upkarlidder changed the title Data gathering (Collect More Data/Track) Epic - Data gathering (Collect More Data/Track) Jan 28, 2022
@sforsyth089
Copy link
Collaborator Author

Refer to assets for the latest list.

@github-actions
Copy link

github-actions bot commented Apr 1, 2022

👋 Hi! This issue has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed.

@github-actions github-actions bot added the stale label Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

5 participants