Skip to content

Removed references to AREA_ID_FOOTPRINT#89

Open
EmilyMarkowitz-NOAA wants to merge 6 commits into
mainfrom
68-delete-area_id_footprint-column
Open

Removed references to AREA_ID_FOOTPRINT#89
EmilyMarkowitz-NOAA wants to merge 6 commits into
mainfrom
68-delete-area_id_footprint-column

Conversation

@EmilyMarkowitz-NOAA
Copy link
Copy Markdown
Contributor

While we were making improvements to the data, I thought it would also be good to integrate this change. AREA_ID_FOOTPRINT is a descriptive version of AREA_ID, and needs to be removed in this next new version of this table.

… as AREA_ID (and is completely descriptive and doesnt match with what is in the area table
@EmilyMarkowitz-NOAA EmilyMarkowitz-NOAA linked an issue May 13, 2026 that may be closed by this pull request
2 tasks
@EmilyMarkowitz-NOAA EmilyMarkowitz-NOAA added bug Something isn't working enhancement New feature or request labels May 13, 2026
@EmilyMarkowitz-NOAA EmilyMarkowitz-NOAA changed the title removed references to AREA_ID_FOOTPRINT - redundant and not as useful… Removed references to AREA_ID_FOOTPRINT May 13, 2026
@zoyafuso-NOAA
Copy link
Copy Markdown
Collaborator

This comment is associated with this issue (#68 )

This is what is currently in my head about how to do this change safely:

  • Disable the trigger on AGECOMP that writes to AUDIT_AGECOMP
  • Drop the constraints on AGECOMP that rely on AREA_ID_FOOTPRINT
  • Create a temporary field AREA_ID_FOOTPRINT_TEMP NUMBER(5,0) for both AGECOMP and AUDIT_AGECOMP
  • Map out the old VARCHAR2 values in AREA_ID_FOOTPRINT onto the temporary field (e.g., “EBS Standard Area” -> 99901) for both AGECOMP and AUDIT_AGECOMP
  • Drop the old field and rename the temp field to AREA_ID_FOOTPRINT
  • Recreate the constraints and triggers
  • Alter the production.R script to account for this change to NUMBER as you have here.
  • Hope everything works out?

I imagine this would also need to happen on the AKFIN side as well. There is a chance that something could go wrong in this process and I won’t have time to troubleshoot before releasing new data post survey this year. I would rather do this process after this season and work this out either when we get the first pollock ages or next Spring when we get another batch of ages.

I know I’ve been putting this off for years now but if this is important to integrate, I would prioritize this safely happening for 2027.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Delete AGECOMP/AKFIN_AGECOMP.AREA_ID_FOOTPRINT column

2 participants