chore(data): drop unattributed alternate IDs from the ingested San Acacia wells - #857
Merged
Merged
Conversation
…acia wells Each of the 38 wells this pipeline reads carries two identifier links: an NMBGMR one and an "Unknown" one with no recorded provenance. Mostly they duplicate. Sometimes they contradict -- SO-0131 has NMBGMR "BRN-E04B (shallow)" against Unknown "BRN-E04A" while SO-0132 has them reversed, so the two sources disagree about which physical well is which (BDMS-1168). Removing the unattributed rows leaves NMBGMR as the single answer. An identifier nobody can source is worse than none, because it reads as corroboration. Scoped to the 38 ingested wells deliberately. The wider reach network has 152 such links and every SO- well has 263; widening is a separate decision, and 19 of the reach network's links are the conflicting ones BDMS-1168 tracks -- deleting those would remove the evidence along with the conflict. Wells are matched by name rather than id so the migration means the same thing in every environment, and a well missing by name is reported rather than passed over silently. Verified against staging: 38 wells matched, each with one NMBGMR and one Unknown link, so it removes 38 rows and leaves every NMBGMR identifier intact. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Coverage✅ 77.96% total — gate is 75%. Coverage for the Python files changed in this PR
|
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
1 participant
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.
Data migration
20260819_0001_drop_unknown_alternate_ids.Each of the 38 San Acacia wells this pipeline reads carries two identifier
links: an
NMBGMRone and anUnknownone with no recorded provenance. Mostlythey duplicate. Sometimes they contradict:
BRN-E04B (shallow)BRN-E04ABRN-E04A (deep)BRN-E04BThe two sources disagree about which physical well is which (BDMS-1168).
Removing the unattributed rows leaves NMBGMR as the single answer — an
identifier nobody can source is worse than none, because it reads as
corroboration.
Scope: the 38 ingested wells, deliberately
SO-wellsWidening is a separate decision, and not a neutral one: 19 of the reach
network's 152 links are the conflicting ones BDMS-1168 is tracking. Deleting
those removes the evidence along with the conflict. The other 133 are
byte-identical duplicates.
Note the database also has a group literally named "San Acacia" — 42
different wells,
SAC-prefixed, of which none are the Diver-HUB points.Worth knowing before anyone scopes future work by that name.
Safety
environment. A well missing by name is reported rather than passed over.
alternate_organization = 'Unknown'is touched. NMBGMR, PLSS, NMOSE,USGS, NMED and TWDB links are untouched.
one Unknown link. Removes 38 rows, leaves all 38 NMBGMR identifiers.
b2c3d4e5f6a7, not repeatable.Reminder
Data migrations have no CD path — this will sit unapplied until run by hand.
🤖 Generated with Claude Code