NYCPlanning / NYCPlanning/data-engineering
CSCL - Potential transformation enhancements
Open
Nobody has claimed this yet.
db-cscl
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
Currently not really scoped, but want to capture these as they come along.
Lowest hanging fruit
- #2193 -> clear bug in prod that could be resolved in our pipeline
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing issue #2193 and the existing transformation pipeline. Identify which enhancements are intended to be included and define a bounded change before implementation. Done should mean that the agreed transformation improvements are implemented and the production bug in #2193 is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100