NYCPlanning / NYCPlanning/data-engineering
GDE data flows
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43
- Forks
- 3
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 44
Description
in order to document the current GDE data flows, we should list and describe our:
- data source systems
- dataset destinations
- direct data users/consumers
- owner of each step in the data flow
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
No file, test, or documentation entry point is named. Start by locating the existing GDE documentation and current data-flow records, then identify the source systems, dataset destinations, direct consumers, and owner for each step. Done means the current flows are listed and each requested role is described.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100