Glavin001/Data2AITextbook

Truecasing of poorly written answers

Open

#3 opened on Aug 19, 2023

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Jupyter Notebook (3 forks)github user discovery
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (26 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Contributor guide

Research direction
Read the linked article on truecasing, understand the technique, then identify poorly written answers in the dataset and apply truecasing to fix them.
Tech stack
None
Domain
data
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
basic NLP concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60