Skip to content

BDMS 122: map lookup table codes to lexicon terms#136

Closed
jacob-a-brown wants to merge 9 commits into
stagingfrom
jab-lexicon-lookup-tables
Closed

BDMS 122: map lookup table codes to lexicon terms#136
jacob-a-brown wants to merge 9 commits into
stagingfrom
jab-lexicon-lookup-tables

Conversation

@jacob-a-brown

Copy link
Copy Markdown
Contributor

Why

This PR addresses the following problem / context:

  • The new ocotillo database uses the full terms instead of the lookup table codes. If we just transfer the codes (which are present in the various tables like Location and WellData) then foreign key errors will be raised. This mapper enables the transfer scripts to transfer the correct data.

How

Implementation summary - the following was changed / added / removed:

  • Read lookup table csvs from bucket and map mapper

Notes

Any special considerations, workarounds, or follow-up work to note?

  • Use bullet points here

@jacob-a-brown jacob-a-brown requested review from jirhiker and removed request for jirhiker September 12, 2025 17:53
@jacob-a-brown

Copy link
Copy Markdown
Contributor Author

Many LU tables share the same code (e.g. M). To allow the same code from multiple tables to be used the table name has been prepended to the key as {table name}:{code}.

@jacob-a-brown

Copy link
Copy Markdown
Contributor Author

These updates will be in a future PR for location transfer revision

@TylerAdamMartinez TylerAdamMartinez deleted the jab-lexicon-lookup-tables branch February 5, 2026 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant