NYCPlanning / NYCPlanning/data-engineering
DevDB - determine capture date vars from version
Open
Nobody has claimed this yet.
db-developments
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
CAPTURE_DATE and CAPTURE_DATE_PREV are used in DevDB, and must be updated manually in recipe. These could be determined and set logically from the version (23Q4 -> 2024-01-01 and 2023-07-01 for date and date_prev, respectively)
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 locating the DevDB recipe and the code that parses or receives its version value. Trace how CAPTURE_DATE and CAPTURE_DATE_PREV are currently supplied, then verify that versions such as 23Q4 produce 2024-01-01 and 2023-07-01 without manual recipe updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100