Add data and other to EIA 176 raw data extraction

[e-belfer]

Overview

This PR builds on #3227 and adds data and other 176 data to the extraction process designed by @davidmudrauskas, transforming the extractor function into a dagster asset factory to enable simple creation of a dagster asset for each table.

What problem does this address?

Extracts raw EIA 176 "data" and "other" tables.

What did you change?

Converted the extractor in pudl.extract.eia176 to a factory, and added to the table_file_map.csv. Updated the unit test to handle multiple files, rather than just one.

Testing

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

Generate the raw assets in dagster and open them to review.

Remaining questions

• EIA 176 zipfiles also bundle a few other forms - 191 and 757. Where do we want to extract and process these datasets? As separate modules, or as part of the EIA 176 extraction? If in this module, we'll want to adapt the table_file_map.csv to account for the fact that there are multiple data CSV files, one per form.

To-do list

Edit tasklist title

Beta Give feedback Tasklist To-do list, more options

• Rename
• Copy markdown
• Delete tasklist

Delete tasklist

Delete tasklist block?

Are you sure? All relationships in this tasklist will be removed.

Cancel Delete

1. Make sure full ETL runs & `make pytest-integration-full` passes locally

   Make sure full ETL runs & make pytest-integration-full passes locally
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
2. If updating analyses or data processing functions: make sure to update or write data validation tests

   If updating analyses or data processing functions: make sure to update or write data validation tests
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
3. Update the [release notes](../docs/release_notes.rst): reference the PR and related issues.

   Update the release notes: reference the PR and related issues.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
4. Review the PR yourself and call out any questions or issues you have

   Review the PR yourself and call out any questions or issues you have
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove

Add item to To-do list Loading

[zaneselvans]

Responding to this question in #2603 since I think it's more broadly related to our integration of EIA's natural gas data:

EIA 176 zipfiles also bundle a few other forms - 191 and 757. Where do we want to extract and process these datasets? As separate modules, or as part of the EIA 176 extraction?

See this comment

[zaneselvans]

I think we should stick with the dataset ID eia176 and never introduce an _ in here. It's nice to be able to search for these IDs reliably and use the same idioms for all the datasets like eia860, eia861, eia923 etc.

[e-belfer]

You mean in the function names? Simple enough fix, that makes sense.

[zaneselvans]

Function names, variable names, tables, classes, anywhere we're naming something to refer to the dataset.

[zaneselvans]

Not sure what we'll want to do about the mish-mash of different forms that were hiding inside this zipfile.

[e-belfer]

Closing this PR, in order to address changes to the underlying data format and needed extraction code changes in a separate issue.

[zaneselvans]

@e-belfer can we delete the eia176_extraction branch?