CBBR source data questions

Open
#2,700 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active

Research direction

Start by reviewing the Open Data Preliminary, Executive, and Adopted editions linked in the issue alongside the CAPS export and FY2027 omb_cbbr_agency_responses comparison. Resolve whether trkno can be added to the export and which agency explanations are required. Done means the source fields, joins to dcp_cbbr_requests, and replacement of the OMB-to-CAPS-to-DE handoff are clearly decided.

Written by the indexing model from the issue text.

Description

db-cbbr

Two questions for CAPS:

  1. Can the request export include the OMB tracking code (trkno)?
  2. Does CBBR need the agency explanations from the Preliminary register, or would the Executive and Adopted text on Open Data do?

OMB publishes all three editions of the Register of Community Board Budget Requests on Open Data. If the answers are yes, we could build CBBR from Open Data plus the CAPS export and drop the OMB -> CAPS -> DE handoff for omb_cbbr_agency_responses.

Comparing our FY2027 omb_cbbr_agency_responses to the Open Data Preliminary edition, all 3,809 rows join on trkno = tracking_code. For the OMB columns the build uses:

OMB column Open Data
trkno, priority, agency_response match 100%
reason, lowsgrp1/2 match 99%+
type, agency_acronym derivable from tracking_code and responsible_agency
budline1-3, capis1-3 missing, but always null in OMB's file
explanation missing
dcpuniqid missing

Why Open Data can't replace the OMB file today:

  • No dcpuniqid, so no way to join to dcp_cbbr_requests for title, policy area, and location fields. The CAPS export has no tracking code. Open Data's own location fields don't fill the gap (123 of 3,809 rows have a bbl).
  • The Preliminary edition has only the response category, not the agency explanation (our agency_response column). Explanations show up starting with the Executive edition, for 1,831 of 3,809 requests.
Dominant language
Python
Stars
2
Forks
0
Avg merge
13h 8m
Merged PRs (30d)
138

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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.

More from NYCPlanning/data-engineering

All issues in NYCPlanning/data-engineering

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.