Add missing eia923 file mappings discovered in audit#4317
Draft
Add missing eia923 file mappings discovered in audit#4317
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Overview
What problem does this address?
While checking mappings for #4312 we discovered some pages of existing source spreadsheets weren't being mapped but sh/could have been. This PR adds those missing mappings back in.
NOTE: we're not currently extracting any of this data because it's not column-mapped...but it is file and pagemapped, and we seem to be maintaining those mappings, so this correction is still probably good to do
What did you change?
coal_stocksandpetcoke_stocksfor 2021, 2022, 2023coal_stocks2017Documentation
Make sure to update relevant aspects of the documentation:
docs/data_sources/templates).src/metadata).Testing
How did you make sure this worked? How can a reviewer verify this?
& the results are all Puerto Rico (which is getting handled in #4312) and Boiler/Generator (which all have identical counterparts already mapped; apparently EIA includes those tables in two separate spreadsheets):
To-do list
dbttests.make pytest-coveragelocally to ensure that the merge queue will accept your PR.make pytest-coveragepasses, make sure you have a fresh full PUDL DB downloaded locally, materialize new/changed assets and all their downstream assets and run relevant data validation tests usingpytestand--live-dbs.make pytest-validate.build-deploy-pudlGitHub Action manually.