NYCPlanning / NYCPlanning/data-engineering
DevDB - migrate build SQL to dbt
Open
Nobody has claimed this yet.
db-developments
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
Unmet success criteria: 3, 4, 5, 6
39 .sql files in sql/. dbt project has no models.
some diagrams were started in https://github.com/NYCPlanning/data-engineering/issues/1093
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 the 39 SQL files in sql/ and the currently empty dbt project to understand the migration scope. Check the diagrams and related work in issue 1093, then use success criteria 3–6 as the completion checklist for the dbt models.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100