Identify Data Gaps or Needs for Each Step (Based on User Stories)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- data, documentation
Research direction
Start by reviewing the user stories and the related feature updates to identify each step and the data it uses. Mark the data entering and leaving every step, then document any missing or still-needed data as the completion criterion.
Written by the indexing model from the issue text.
Description
Background on the problem the feature will solve/improved user experience
Based on reviewing/implementing updates from the user stories, work on figuring out any data missing or still needed. Document clearly.
Describe the solution you'd like
Once User Stories put into place, figure out if all data is there or more is needed. Document clearly.
Acceptance Criteria
Mark the data going into / out of each step. Document clearly any gaps.
- Dominant language
- No language data
- Stars
- 76
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Call-for-Code-for-Racial-Justice/Open-Sentencing
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
ETL for Race Data Openstale
Difficulty 5/5 Over a week Newbie friendliness 25/100
Call-for-Code-for-Racial-Justice/Open-Sentencing#78 · 1 comment ·
-
non-technical stale
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Call-for-Code-for-Racial-Justice/Open-Sentencing#71 · 1 comment ·
-
documentation stale
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Call-for-Code-for-Racial-Justice/Open-Sentencing#70 · 1 comment ·
-
enhancement keep-open
Call-for-Code-for-Racial-Justice/Open-Sentencing#68 · 1 comment · 2 assignees ·
All issues in Call-for-Code-for-Racial-Justice/Open-Sentencing
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cisagov/cyhy-reports#149 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
open-compass/VLMEvalKit#1698 ·