-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add SFCLAM metadata doc #44
Comments
Need to include this. BACKGROUND: Since the inception of SF/OQ vessel logbook reporting, SF/OQ data has resided in its own schema, SFCLAM. Further, reported bycatch of non SF/OQ species from those trips were reported separately via a Vessel Trip Report (VTR) and resided in the VTR database commonly known as CATCH, IMAGES, DOCUMENT (CID). As part of the regional effort to modernize our fisheries dependent data collection systems; On November 1, 2024, GARFO will begin inserting all new SF/OQ data into CID while also continuing to insert it into SFCLAM. All legacy data prior to November 1, 2024 will only be accessible in SFCLAM. There are no plans at this time to migrate legacy SFCLAM data into CID. If you have historically joined the SFCLAM and CID tables to query vessel records, you may need to modify your code to avoid duplicating results. End users may notice a minor change to the SF/OQ data format; specifically, a new column (RECORD_SOURCE VARCHAR2 in SFCLAM.SFOQVR) indicating where the data has been sourced from. Possible data values are: “Unconverted Due to Age” = Legacy data only accessible in SFCLAM and not in CID or the originating eVTR trip reports system. “Converted Successfully”= SF/OQ data inserted into SFCLAM and CID originating in the eVTR trip reports system. Of note, cage tags associated with Surf Clam catch will not be contained in CID. A sample query to join tag data to CID/SFCLAM is provided below. For assistance,please contact EvertJan Vantland, GARFO Lead Software Engineer, at evertjan.vantland@noaa.gov. Sample query of how to join tag data to CID/SFCLAM:
|
no SFCLAM documentation.
The text was updated successfully, but these errors were encountered: