Repository navigation
chore: 🍱 update field resource mapping based on raw data - #135
Merged
Merged
Conversation
…in raw data) Missed it in prior commit.
…completion time fields
lwjohnst86
requested changes
Oct 29, 2026
lwjohnst86
approved these changes
Oct 29, 2026
lwjohnst86
left a comment
Member
There was a problem hiding this comment.
I'll merge this in so that you can extract from the raw data instead.
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.
Description
For #37, I needed this mapping to be aligned with the raw data, so I went ahead and compared them.
This includes:
__dropped__to descriptive fields/fields not in the raw data - only in the data dictTo be descriptive of why some fields are dropped and which fields are only in the raw data, I went ahead and added a "comments" column.
Closes #129
Needs a thorough review.