NYCPlanning / NYCPlanning/data-engineering
COLP - improve QAQC reports (not in necessarily in QA app)
Open
Nobody has claimed this yet.
db-colp
QA
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
Feedback from LS
usetype_changes.csv
- columns are switched – num_records_current is the old version, num_records_previous is the new version. Diff shows decrease when there is an increase
- Add new field with percentage change
- Report does not include usetypes that are in the current version, but not the previous version (not sure if the reverse is true)
ipis_modified_names
- Add flag to show which records had their display name updated through from manual modifications (rather than programmatic changes)
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 code that produces the usetype_changes.csv and ipis_modified_names reports. Review how current and previous counts, usetypes, and display-name changes are determined. Done means the requested percentage, missing-usetype, and manual-modification indicators appear correctly in the reports; no test files are mentioned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100