ProcessingLevelDescription

[smk0033]

pyQuARC flags for a ProcessingLevelDescription that is too short, but does not flag for a missing description. The ProcessingLevelDescription check should be modified or a new check should be added to ensure that something is provided.

ARC recommendation for a missing Processing Level Description (blue/info):

""Recommend providing a processing level description, using the EOSDIS processing level descriptions as guidance:

https://www.earthdata.nasa.gov/engage/open-data-services-and-software/data-information-policy/data-levels"

[smk0033]

PR: #310

[FBayat021]

Referencing the notes here

Processing Level Description:

• If the processing level description field is missing, the following message should appear (BLUE/Info):

"Recommend providing a processing level description, using the EOSDIS processing level descriptions as guidance:
https://www.earthdata.nasa.gov/engage/open-data-services-and-software/data-information-policy/data-levels"

• If a processing level description is provided but it has fewer than 50 characters, then the following message should appear (BLUE/Info):

"The description provided is under 50 characters. Recommend providing a more detailed processing level description, using the EOSDIS processing level descriptions as guidance:
https://www.earthdata.nasa.gov/engage/open-data-services-and-software/data-information-policy/data-levels"

Processing Level Id
We reached out to ESDIS, and they confirmed that the correct formatting for the Processing Level Id is as follows: [0, 1A, 1B, 1C, 2, 2A, 2B, 3, 3A, 4]. For example, entries such as "Level 0" or "Level0" are not valid; instead, the value should simply be "0". For more, please refer to KMS controlled vocabulary schema.

[lavanya3k]

See the updated PR for code merge #327