Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add backlogged age data from fram_central (postgres prod) to the data warehouse #72

Open
BHHorness-NOAA opened this issue May 17, 2020 · 1 comment
Assignees

Comments

@BHHorness-NOAA
Copy link
Collaborator

BHHorness-NOAA commented May 17, 2020

As age_facility qualifiers were being added into the data warehouse individual_fact table (#71), several age data sets were found to be absent. These will need to be added after the ageing facility data have been added. So, the missing age data belong to the following groups:

Ages read in 2016 and 2017; this should be checked to confirm which age data lots are truly absent
POP ages read in 2014; master specimen analysis lots 375 and 376.
POP ages read in 2015; master specimen analysis lot 406

It was also noted that the 2014 Pacific Hake ages read in 2018 (master specimen analysis lot 423, 424) were selected to support maturity analysis. The age structures were collected randomly in the field, but the subset selected for ageing was non-random. So, these ages were not transferred to the data warehouse. It is likely that they will be wanted by users. If those ages are added, then it is unclear what the Standard_Survey_whid should be. The age structures were randomly collected in the field (Standard_Survey_whid = 1), but the age reads were not randomly conducted (Standard_Survey_whid = 28). The standard_survey_whid has been set based on field collections, so this variant would be a departure. Since they should not be included in assessments, the standard_survey_whid should be set to 28 if the nonrandomly read ages are added to the warehouse.

@SaOgaz-NOAA
Copy link
Contributor

Hi @BHHorness-NOAA, same question here, any updates?

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

No branches or pull requests

2 participants