NYCPlanning / NYCPlanning/data-engineering
PLUTO - migrate build SQL to dbt
Open
Nobody has claimed this yet.
db-pluto
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
Unmet success criteria: 4, 5, 6
81 .sql files in pluto_build/. 40 staging and 15 intermediate models; 1 product model.
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 81 SQL files in pluto_build/ and the unmet success criteria 4, 5, and 6. Determine the required dbt structure and migration boundaries before proceeding; done means the listed staging, intermediate, and product models have been migrated and all success criteria are met.
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