Completed missions not passing compliance checker due to qartod variables

What went wrong?

Hi There,

When checking on our completed missions to see if they have successfully been sent to NCEI I now see errors related to DAC supplied QARTOD variables.

On page https://gliders.ioos.us/providers/users/jpsevadjian/deployment/64fcec6dbcab6800096055f3, I see:

Compliance Check Report CF standard name errors must be fixed prior to NCEI archival:

Attribute long_name or/and standard_name is highly recommended for variable qartod_monotonic_pressure_flag

Another mission page (https://gliders.ioos.us/providers/users/jpsevadjian/deployment/660ef6ab24c258000aec233c) shows an additional error:

Compliance Check Report CF standard name errors must be fixed prior to NCEI archival:

Attribute long_name or/and standard_name is highly recommended for variable qartod_monotonic_pressure_flag Attribute long_name or/and standard_name is highly recommended for variable qartod_location_flag

I believe these are issues to be resolved by the DAC implementation of QARTOD and are similar to those reported in issue 382.

Should we be concerned about these errors and are they preventing our data from being submitted to NCEI?

Thanks, Jenn

Operating System

macOS

Version

12.7.1

Python Version

3.9

Code to Reproduce

None. Visit https://gliders.ioos.us/providers/users/jpsevadjian/deployment/660ef6ab24c258000aec233c](https://gliders.ioos.us/providers/users/jpsevadjian/deployment/660ef6ab24c258000aec233c to see the message.

Errors, Traceback, and Logs

Compliance Check Report
CF standard name errors must be fixed prior to NCEI archival:

Attribute long_name or/and standard_name is highly recommended for variable qartod_monotonic_pressure_flag
Attribute long_name or/and standard_name is highly recommended for variable qartod_location_flag

ioos / glider-dac