Recode Additional Fields - Githubissues

NYCPlanning / db-zap-opendata

Workflow for creating subset of ZAP data that's on open data

0 stars 0 forks source link

Recode Additional Fields #25

Closed SashaWeinstein closed 2 years ago

SashaWeinstein commented 2 years ago

This is a continuation of issue #15 Two additional upgrades from Matthew

Fields with coded values still present:

ceqr_leadagency (e.g. 0014e50f-1133-e811-8126-1458d04dc8c8)
primary_applicant (e.g. 926ff192-1abc-ea11-a812-001dd8309c75)
current_milestone (e.g. 3eaae86c-bdcf-eb11-bacf-001dd8049160)
current_envmilestone (e.g. 0066963c-52c5-eb11-8235-001dd804b354)

In the dcp_projectsbbls table:

project_id: this is still showing values that contain project id and bbl values (e.g. 2020R0189 - 5 - 05602 – 0034, instead of just 2020R0189).

Is this using "dcp_project" as source field in ZAP?
If yes, can we strip out the lot info so the value only displays actual project id? This is needed so the bbl records can be joined back to the project records.

SashaWeinstein commented 2 years ago

Update: Buji sent this link to get human-readable names for a single project https://nycdcppfs.crm9.dynamics.com/api/data/v9.1/dcp_projects(25e3308e-3947-43ea-9fd7-22d4c3a0c095)?$select=_dcp_applicant_customer_value,_dcp_currentmilestone_value,dcp_name&$expand=dcp_CurrentMilestone($select=dcp_name),dcp_leadagencyforenvreview($select=name),dcp_applicant_customer_contact($select=fullname),dcp_currentenvironmentmilestone($select=dcp_name),dcp_applicant_customer_account($select=name)] We are meeting on thursday to discuss the best way to get metadata for each of the 4 fields across all projects. It may involve iterating through each project though hopefully there is an easier way