'ProcessingLevel/ProcessingLevelDescription'

[lavanya3k]

A new feature 'ProcessingLevel/ProcessingLevelDescription' rule (Check #549) has be added.

[lavanya3k]

Describe the bug: PyQuARC did not flag the collection ProcessingLevel/ProcessingLevelDescription with or without the ProcessingLevel/Id. If the processing level is available [0, 1A, 1B, 1C, 2 or 3], the processing level description is checked for the characters. If the characters are less than 50, then an info message is generated.
The above bug fix works when the correct processing level is present. But, to be consistent in the error message, ProcessingLevel/ProcessingLevelDescription needs to be updated when the characters are under 50, and blue info warning.

To reproduce: Example: C1602481912-CDDIS -ProcessingLevel/ProcessingLevelDescription < 50 and info message (blue).
C2043197582-CDDIS umm-c format - Info message for ProcessingLevel/ProcessingLevelDescription.
C1000000005-CDDIS umm-c format - Works correct.

Expected behavior: Any collection record, irrespective of the number of characters, should provide the details for the processing level description.

[bhawana11]

Works on CDDIS record. The following records were used for the testing:
C1000000042-CDDIS
C1000000006-CDDIS
C2043197582-CDDIS
C1291967305-CDDIS
C2978524117-CDDIS

C179014695-NSIDC_ECS - For this record, PyQuARC flags the processing level description with an error message saying that the characters are less than 50. This is still in consistency with other records where the processing level description is required. We are not sure if the error message has to be consistent. ?
Another issue with the collection ID - PyQuARC flags the processing level ID [‘Level 3’] as a yellow flag, but this was not flagged in the CMR Dashboard. According to EOSDIS, processing level IDs are in the following format [0, 1A, 1B, 1C, 2, 2A, 2B, 3, 3A, 4.

[FBayat021]

Before merging the changes in this PR, please double-check the following:

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

Hold off on making any changes to the error message that appears for the "ProcessingLevel / Id" element. We're currently waiting for ESDIS to confirm the correct formatting that should be recommended both in our manual curation process and in pyQuARC (e.g., "Level 0" vs. "Level0" vs. "0").

[FBayat021]

Update on Processing Level Id: We heard back from 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]

Moved changes to the new PR #323, hence closing this PR.