Updating ntd_id_2022 using airtable #3367
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In a previous #3364 PR a formula was used to generate ntd_id_2022, but it's better to put it in airtable. This way joins from airtable table have this id available easily especially when one might want to join to other more recent ntd data.
Separately using a csv join ntd_id_2022 was calculated and added to the orgs table. This also removes that calculation.
Type of change
How has this been tested?
local airflow
poetry run dbt run -s +dim_organizations
Post-merge follow-ups