NYCPlanning / NYCPlanning/data-engineering
automating upload of GR QA data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
In the second month of every quarter, GIS uploads GR files to edm-publishing so we can run QA reports for GR to review (see example GIS issue here).
Since this process is repetitive and doesn't involve modifying data, GDE would benefit from automating this process.
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 linked GIS issue and documenting the current process for uploading GR files to edm-publishing. Identify the existing entry point for uploads and how QA reports consume the files. Done means the recurring second-month-of-quarter upload is automated without modifying the data and produces inputs that GR can review through the QA reports.
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
- 25/100