NYCPlanning / NYCPlanning/data-engineering

review records in `nycourts_courts`

Open
#1,068 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

db-facilities ingest/library
Dominant language
Python
Stars
43
Forks
3
Avg merge
23h 3m
Merged PRs (30d)
44

Description

nycourts_courts is only used in FacDB

we manually maintain the records in nycourts_courts by reviewing this site and making changes if we see any. we haven't made changes since 2021 and I don't see any new details for the records we currently have

but these records seem to be a subset of "courts" in NYC (e.g. no civil courts) and this site seems like a better resource for their addresses

what determines the types of courts we should have in FacDB?

the only other apparent dataset related to courts in FacDB is uscourts_courts

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the two linked NYC Courts sources and compare them with the existing nycourts_courts and uscourts_courts records in FacDB. Determine which court types and address source should be represented; done when the scope and any resulting record changes are agreed.

Written by the indexing model from the issue text.

Assessment

Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.