NYCPlanning / NYCPlanning/data-engineering
CSCL - Resolving Data Discrepancies
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
This will capture the cross-team work of reviewing and resolving differences between dev and prod CSCL files
sub-issues can be created to cover any desired level of detail, especially as places for DE to document details and finding.
The CSCL ETL - Issue tracking excel file in SharePoint is how DE and GR are coordinating on distinct issues.
The Data Discrepancy Tracking folder in SharePoint is where the tracking sheet and any other helpful documents live. Word docs are helpful for sharing more details, screenshots, and comments that could not go in the tracking sheet.
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.
Assessment
This issue has not been assessed yet.