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.

Sign up for GitHub

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

Jump to bottom

Get double read of otoliths into PacFIN #107

Open
kellijohnson-NOAA opened this issue Apr 6, 2023 · 1 comment
Open

Get double read of otoliths into PacFIN #107

kellijohnson-NOAA opened this issue Apr 6, 2023 · 1 comment
Labels
priority: low The lowest level priority, i.e., not urgent. status: long term A long-term problem that could potentially be a change needed in PacFIN. topic: database Related to information in or access to the PacFIN database, stuff outside of our control type: enhancement
Milestone
year_2027

Comments

@kellijohnson-NOAA
Copy link
Contributor

In theory, we no longer have to ask for age reads b/c the information is contained in the bds pull. But, Patrick noted that he doesn't send all double reads to the state-specific data bases. I will work on getting these to PacFIN. Sent reminder email on 2022-05-04. Brad from PacFIN is also working on the data structure inside PacFIN BDS data to store these double reads. This is a long-term issue that is beyond this repository but still needs to be addressed.

Originally posted by @kellijohnson-NOAA in #35 (comment)
@kellijohnson-NOAA kellijohnson-NOAA added status: long term A long-term problem that could potentially be a change needed in PacFIN. topic: database Related to information in or access to the PacFIN database, stuff outside of our control type: enhancement labels Apr 6, 2023
@kellijohnson-NOAA kellijohnson-NOAA added this to the year_2025 milestone May 8, 2023
@kellijohnson-NOAA kellijohnson-NOAA added the priority: low The lowest level priority, i.e., not urgent. label May 9, 2023
@kellijohnson-NOAA kellijohnson-NOAA mentioned this issue May 27, 2023
Open
3 tasks
@kellijohnson-NOAA kellijohnson-NOAA modified the milestones: year_2025, year_2027 Nov 4, 2024
@kellijohnson-NOAA
Copy link
Contributor Author

I mentioned this at the PacFIN meeting but it is still an ongoing issue that will need to be brought up again. I think another potential way forward would be to try to get funding to create a new table within PacFIN to store all of this information. Funding might be needed to create the table. Marking with future milestone for right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: low The lowest level priority, i.e., not urgent. status: long term A long-term problem that could potentially be a change needed in PacFIN. topic: database Related to information in or access to the PacFIN database, stuff outside of our control type: enhancement
Projects
None yet
Milestone
year_2027
Development

No branches or pull requests
1 participant
@kellijohnson-NOAA