Null request ids for cbbrs

[TangoYankee]

Description

90 rows are NULL for the request_id column of the community_board_budget_request table. This is more than the source data. (The source data should not have any null request ids. Though, there is one null request id for a probably unrelated reason. Knowing that one value is null means we have 89 more to account for)

Acceptance criteria

• The number of null entries in the request_id column of community_board_budget_request table matches the source data

[TangoYankee]

Sources:

• The export of all budget requests
• The relationship between all options (aka the options cascade)
• Distinct entries for each option (aka the options, no duplicates)

Discrepencies between sources:

• The options cascade and the distinct options sources seem to differ on the request of "Create or promote programs to decrease children's emergency department visits for asthma and prevent injuries".
  • It seems they use a different character for the possessive apostrophe in "children's"
  • No budget requests seem to use this value in export
• The white space differs between budget request export and options
  • No values in the budget request export have a leading whitespace character
  • The following values have a leading whitespace character in the options lists
    • " Create a neighborhood plan in coordination with the community"
  • No values in the budget request export have a trailing whitespace character
  • The following values have a leading whitespace character in the options lists
    • "Enhance park safety through design interventions, e.g. better lighting "
    • "Increased community board training, including on core land use process and practices "
    • "Invest in capital projects to improve access to waterfront "
    • "Invest in infrastructure that will support growth in commercial business districts "
    • "New equipment for maintenance "
    • "Other cultural facilities and resources requests "
    • "Other NYPD facilities and equipment requests "
  • Trimming the options leads to 41 more matches (only 48 left to account for)
• The phrasing of "capital request" differs between agencies in the two sources. Some include the word "budget"
  • The following values exist in the budget request export but not in the options lists (accounting for 13 nulls)
    • "Other capital request for DCP"
    • "Other capital request for DOE"
    • "Other capital request for DOHMH"
    • "Other capital request for DOITT"
    • "Other capital request for DOT"
    • "Other capital request for DPR"
    • "Other capital request for EDC"
    • "Other capital request for HPD"
    • "Other capital request for NYCTA"
• The phrasing of "expense request" differs between agencies in the two sources. Some include the word "budget"
  • The following values exist in the budget request export but not in the options lists (accounting for 27 nulls)
    • "Other expense request for DCAS"
    • "Other expense request for DCP"
    • "Other expense request for DEP"
    • "Other expense request for DFTA"
    • "Other expense request for DHS"
    • "Other expense request for DOB"
    • "Other expense request for DOE"
    • "Other expense request for DOHMH"
    • "Other expense request for DYCD"
    • "Other expense request for EDC"
    • "Other expense request for HRA"
    • "Other expense request for LPC"
    • "Other expense request for NYCTA"
    • "Other expense request for OMB"
    • "Other expense request for SBS"
    • "Other expense request for SCA"
• Values are missing from the options list but are present in the export (accounting for 7 nulls)
  • "Improve parking operations"
  • "Provide or expand NYC organics collection program"

[TangoYankee]

@dhochbaum-dcp I think I misunderstood how request values are selected by users in Alchemer. My working model is that users select from a list of possible values within the Alchemer site. The "cbbr options cascade" and "cbbr options no duplicates" (both available in our DO Spaces)are the exact options used in the Alchemer site. However, it seems several values do not have a corresponding match in the options files. Also, one budget request has request that is "null" in the source data.

Would you or the CAPS team have insight into this?