Eia860m eia923 q1 2025

[aesharpe]

Overview

Closes #4038

What problem does this address?

Adds new monthly data from EIA860m and EIA923

What did you change?

• Add new DOIs for both data sources
• Update working partitions for EIA860m (not relevant for 923)
• Update package_data to accommodate new data and changes to old data
• Update release notes
• Update minmax rows test

Documentation

Make sure to update relevant aspects of the documentation.

Tasks

Preview Give feedback

1. Update the release notes: reference the PR and related issues.
2. Update relevant Data Source jinja templates (see docs/data_sources/templates).
3. Update relevant table or source description metadata (see src/metadata).
4. Review and update any other aspects of the documentation that might be affected by this PR.

Testing

How did you make sure this worked? How can a reviewer verify this?

• Materialized assets in dagster
• Ran fast ETL
• Ran tests

To-do list

Preview Give feedback

1. If updating analyses or data processing functions: make sure to update or write data validation tests (e.g. test_minmax_rows()).
2. Run make pytest-coverage locally to ensure that the merge queue will accept your PR.
3. Review the PR yourself and call out any questions or issues you have.
4. For minor ETL changes or data additions, once make pytest-coverage passes, 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 using pytest and --live-dbs.
5. For bigger ETL or data changes run the full ETL locally and then run the data validations using make pytest-validate.
6. Alternatively, run the build-deploy-pudl GitHub Action manually.

[aesharpe]

I tried to see what the other rows from the same coalmine listed as the primary transportation method to see if there was a clear fix here; sadly there was not. Entries from older years say "RV" and newer years say "TR". I chose TR because it's "RT" backwards....also it only affects two entires so it's a very minimal issue.

[cmgosnell]

Looks pretty good to me!! I left some suggestions on the release notes and on the min/max rows.

[cmgosnell]

🎉