Not all standard names are being checked for validity - this prevents archiving by NCEI. #609

Briefly describe the issue

There are files, such as sg686-20251111t1924.nccf.nc3.nc, which are not being archived at NCEI because they have invalid CF standard names. This problem has the potential of preventing a significant number of files from being archived at NCEI. This means that the requirement of having the data archived at NCEI would not be met.

Provide clear, step-by-step instructions

NCEI tried to archive sg686-20251111t1924.nccf.nc3.nc, but was not able to, due to invalid CF standard names. the following notification was sent to glider.dac.support@noaa.gov:

Errors were found during the processing of IOOS NGDAC submissions.
Please contact the NCEI Data Content Manager if you have any questions.

sg686-20251111T1924.ncCF.nc3.nc (2026-06-23 08:50:14)
standard_name "cdom" is not a valid CF Standard Name
This issue prevents NCEI archival of this package.
standard_name "fluorescence" is not a valid CF Standard Name
This issue prevents NCEI archival of this package.
standard_name "backscatter" is not a valid CF Standard Name
This issue prevents NCEI archival of this package.

Expected behavior

Ideally, all data files would be checked for validity of their standard names, and the files would be made available for archiving at NCEI only after all the CF standard names were confirmed as valid.

OS, browser, version, etc.

No response